What Gridinsoft observed on Bloxy.trade
A Gridinsoft threat analyst reviewed the site directly and documented the evidence behind this decision.
GMA-20260905020146-f7e850db
- Reviewed
- by Gridinsoft Threat Analyst
- Analyst finding
- Inconclusive marketplace evidence review
- Evidence basis
- First-party site analysis External vendor intelligence: Not used for this decision
The review distinguishes supported login details, incomplete initial transaction evidence, contradictions in a generated report, and the subsequent explanation and interface images. The latest images partially clarify the purchase, but the complete delivery and payout chain remains unverified. Documentary inconsistencies alone do not prove deliberate fabrication, fraud or phishing.
Analyst findings
Review 5 documented observations View evidence
The earlier review found no Roblox password field in the inspected public login. Supplied OAuth settings showed openid and profile scopes, consistent with the previously inspected fixed callback design. This supported the login explanation; it did not verify private token handling or prove the safety of marketplace transactions.
- Analyst observation What the earlier login evidence supported
The initial 16 images included a disclosed self-deposit/self-withdrawal demonstration, not a sale to a separate buyer. The two game-transfer screens still showed 3.9 and 3.5 seconds remaining. A completed February payout predated the displayed August sale; the rejected payout reason was unopened. A Discord support-entry screen and an unsubmitted ban-message draft did not demonstrate a resolved dispute or refund.
- Analyst observation Why the initial transaction screenshots were insufficient
The sale summary stated a purchase price of $39.00 and seller proceeds of $33.34, while the supposedly linked buyer order listed $0.10. That order was dated May 12, 2026 at 19:22 UTC, but the sequence placed the purchase on September 5, 2026 at 01:13 UTC. The explanation said a successful payout used a different method after a PayPal rejection, yet both payout tables named PayPal.
- Analyst observation Three contradictions in the four-page transaction report
The four-page report supplied a narrative of buyer delivery, completed payout and restoration of a rejected payout to the balance. Its tables and transcribed log line were not independent payment-provider confirmation or original delivery records. The asserted chain mixed incompatible purchase details, so its completion and refund statements could not establish one verified transaction sequence.
- Analyst observation What the prepared report did and did not demonstrate
The operator subsequently explained that the report generator apparently mixed an earlier purchase and withdrawal with a current transaction because the item names matched. Two new interface images show an order marked paid/completed for $39.00 and a sale credit of $33.34, with matching displayed item names and times. This addresses the displayed purchase-price mismatch, but does not independently link final in-game delivery, seller payout and rejected-payout restoration. The operator offered further original records; that offer is not completed verification.
- Analyst observation Subsequent explanation and two additional interface screenshots
Scope and limitations
- This update compares the supplied documentary record and the subsequent explanation. Earlier public-login observations are historical context, not a fresh live-site or authentication test.
- No account was accessed, transaction executed or payment-provider record independently verified. Account identities, transaction identifiers, payment destinations and original private images are not published.
- A completed status in a supplied interface is a displayed claim, not independent proof of settlement. This review does not certify all marketplace trades or use external vendor labels as its decision basis.
