TrueAchievements Banned: Xbox & PS5 Shovelware Publisher Removed from PlayStation Store
TrueAchievements, Notorious Xbox/PS5 Shovelware Publisher, Removed from PlayStation Store After Years of Abuse
Sony has permanently banned TrueAchievements, the long-criticized publisher behind thousands of low-effort “shovelware” titles on Xbox and PlayStation, from its digital storefront following a decade of complaints about fake achievements, broken games, and deceptive marketing practices. The decision, announced June 20, 2026, comes after internal audits revealed the publisher’s titles violated Sony’s Developer Terms of Service for “misleading user engagement metrics” and “repeated pattern of unresolved support tickets.”
The Tech TL;DR:
- Impact on gamers: Players who purchased TrueAchievements titles on PS5/Xbox may face refunds or account restrictions; existing saves/achievements remain unaffected per Sony’s policy.
- Enterprise risk: Publishers using TrueAchievements’ achievement-tracking API (still active on Xbox) must audit integrations for compliance with platform policies.
- Market shift: Sony’s crackdown signals tighter enforcement of its Developer Program Policies, forcing indie studios to adopt stricter QA processes or risk delisting.
Why TrueAchievements Became the Poster Child for Shovelware Exploitation
TrueAchievements’ business model relied on two key technical loopholes:
- Fake achievement inflation: The publisher’s titles—often simple portals or repackaged assets—would artificially inflate achievement counts by triggering “hidden” milestones via
Achievement.UnlockAPI calls without player interaction. According to a 2024 Reddit investigation, one title, *Space Invaders: Remastered*, showed 95% completion after 10 minutes of gameplay. - Exploited platform policies: Sony’s Achievement Guidelines require “meaningful gameplay” for unlocks. TrueAchievements circumvented this by using
achievement_idspoofing in their unofficial SDK, which Microsoft never banned on Xbox.
— Jamie Cross, Lead Security Analyst at GameShield Consulting
“This isn’t just about fake achievements—it’s a case study in how publishers weaponize platform APIs to manipulate user trust. The fact that Microsoft’s Xbox Store never acted on this until now suggests either a lack of enforcement or a willful blind spot in their achievement validation system.”
The Technical Breakdown: How TrueAchievements’ API Worked (And Why It Failed)
TrueAchievements’ achievement-tracking system was built on a custom REST API that interfaced with both Sony’s and Microsoft’s achievement servers. Key technical details:
| Component | Specification | Exploit Vector |
|---|---|---|
TA-API-SDK |
Unofficial wrapper for Sony/Microsoft achievement endpoints (GitHub: link) | Allowed achievement_id spoofing via undocumented headers |
| Server-Side Validation | None on Sony’s end; Microsoft’s Xbox Live used basic checksum validation | Enabled fake “100% completion” milestones |
| Rate Limiting | 200 API calls/hour (vs. Sony’s 50/hour strict limit) | Used to flood achievement servers with fake unlocks |
Sony’s enforcement action hinged on two findings:
- API abuse: TrueAchievements’ titles made 3x more API calls than comparable indie games, per Ars Technica’s network traffic analysis.
- Deceptive metadata: Titles like *Pac-Man: Definitive Edition* (a 2010 asset dump) claimed “40+ achievements” but only 3 were unlockable via actual gameplay.
Code Snippet: How TrueAchievements Spoofed Achievements
// TrueAchievements' undocumented API header to bypass Sony validation
headers = {
"X-TA-Achievement-ID": "fake_12345", // Spoofed ID
"X-TA-Signature": "base64_encoded_placeholder", // No actual validation
"Content-Type": "application/json"
}
response = requests.post(
"https://achievements.playstation.net/v1/unlock",
headers=headers,
json={"player_id": "12345", "game_id": "TA-9876"}
)
print(response.json()) // Returns {"status": "success"} even for fake unlocks
What Happens Next: Refunds, Account Locks, and the Indie Publisher Fallout
Sony’s ban triggers three immediate consequences:
- Refund eligibility: Players who bought TrueAchievements titles between 2018–2026 can request refunds via Sony’s support portal. Microsoft has not announced similar action for Xbox.
- Account restrictions: TrueAchievements’ developer accounts on both platforms are frozen. Existing games remain downloadable but cannot receive updates.
- Indie publisher panic: Smaller studios using TrueAchievements’ white-label achievement system must migrate to compliant alternatives like Steam Achievements or PlayFab.
— Dr. Elena Vasquez, Game Economics Professor at UC Berkeley
“This is a textbook case of how shovelware publishers exploit platform trust. The real victims are indie devs who now face higher scrutiny—anyone using third-party achievement systems will be audited for compliance. The market will shift toward specialized game dev agencies that handle QA and platform compliance in-house.”
How Publishers Can Avoid Sony’s Crackdown: A Compliance Checklist
Sony’s action forces publishers to adopt stricter technical controls. Key steps:
- Audit achievement APIs: Replace any third-party achievement systems with Sony’s official SDK or Xbox Live’s verified endpoints.
- Implement server-side validation: Use
JWTtokens for achievement unlocks (example below):
// Sony's recommended JWT validation for achievement unlocks
import jwt
from datetime import datetime, timedelta
def generate_achievement_token(player_id: str, game_id: str) -> str:
payload = {
"sub": player_id,
"game_id": game_id,
"iat": datetime.utcnow(),
"exp": datetime.utcnow() + timedelta(hours=1),
"achievement_id": "valid_123" // Must match Sony's database
}
return jwt.encode(payload, "SONY_SECRET_KEY", algorithm="HS256")
# Client-side call
token = generate_achievement_token("player_456", "game_789")
headers = {"Authorization": f"Bearer {token}"}
response = requests.post(
"https://achievements.playstation.net/v1/unlock",
headers=headers,
json={"unlock": True}
)
- Monitor API abuse: Deploy game security auditors to detect anomalous traffic patterns (e.g., sudden spikes in achievement unlocks).
The Bigger Picture: Sony’s War on Shovelware and What It Means for Indie Devs
TrueAchievements’ ban is part of a broader crackdown by Sony and Microsoft on “low-effort” content. In 2025, Microsoft removed 1,200 shovelware titles from its store, citing “misleading representations.” The trend reflects:

- Platform economics: Sony’s 70/30 revenue split for indie games makes shovelware unprofitable—TrueAchievements’ titles averaged $2 revenue per title.
- User trust erosion: A 2025 Nielsen report found 68% of gamers avoid stores with known shovelware publishers.
- Regulatory pressure: The EU’s Digital Markets Act (enforced 2024) requires platforms to disclose “meaningful content” policies, forcing Sony to act.
For indie developers, the takeaway is clear: compliance now requires technical rigor. Publishers must integrate platform-native systems or risk delisting. Tools like Unity Achievements or Unreal Online Services offer built-in validation—but audits by specialized game dev agencies are becoming mandatory.
What TrueAchievements’ Fall Means for Your Game’s Achievements
If you’re a developer using third-party achievement systems, ask yourself:
- Is your API key revoked? TrueAchievements’ keys are now invalid; migrate to Sony’s official API.
- Are your achievements “meaningful”? Sony’s guidelines require unlocks tied to “specific gameplay milestones.”
- Do you have a backup plan? Use game security auditors to simulate Sony’s validation checks.
For gamers, the ban means an end to the era of “achievement farming” via shovelware—but it also raises questions about how platforms will police legitimate achievement systems moving forward.
Disclaimer: The technical analyses and security protocols detailed in this article are for informational purposes only. Always consult with certified IT and cybersecurity professionals before altering enterprise networks or handling sensitive data.