Valorant's 11.09 update may have landed back in 2025, but as I queue into Competitive in 2026, its impact is still impossible to ignore. Riot Games used that patch to finally flip the switch on multi-factor authentication for certain accounts, and the ripple effects are still shaping how we talk about smurfs, boosters, and fair play today. Is MFA a silver bullet? No. But it is one of the most direct anti-abuse moves Riot has made in years, and I think it deserves a closer look.
🛡️ The MFA rule that changed Competitive access
Starting with patch 11.09, accounts detected for sharing in NA, LATAM, BR, and KR must enable Riot Mobile multi-factor authentication to access the Competitive queue. Other modes remain unaffected. That detail matters: Riot is not locking people out of Unrated, Swiftplay, or Deathmatch. It is targeting the exact space where smurfing and boosting do the most damage.
Why does account sharing matter so much? Because a shared account can quietly become a smurf account, a booster account, or both. Riot said the MFA announcement was designed to clamp down on smurfs and boosters, and I have seen enough lopsided lobbies over the years to understand the frustration. Smurfs have long used lower-level accounts to ruin other players' days, and some even benefit monetarily from the practice.
Riot also doubled down in mid-September 2025, confirming that certain accounts would be forced to use MFA from 11.09. The update finally arrived, and the message was clear: if an account looks shared or suspected of having different players use it, multi-factor authentication becomes mandatory.
There is more coming, too. All Ascendant+ players will be required to add Riot Mobile MFA to their accounts in the above regions from patch 11.10. That is a big deal for the top end of the ladder, where boosting is often most visible and most profitable.
Riot's reminder is simple: report players for smurfing as Rank Manipulation. Those reports help the team level up its detections. I know reporting can feel like shouting into the void, but in this case the signal genuinely feeds the system.
🔧 Quality-of-life changes that actually help
Beyond MFA, patch 11.09 is full of small quality-of-life fixes. The headline is better highlighting and prioritization for interactive objects. This covers everything your Use Object button does, basically anything where you press F on PC or Square/X on Console by default.
Interactive Object Highlighting now gives world interactions such as switches, ropes, ziplines, and Ultimate Orbs the standard green highlight color used by other interactive objects. Interactive Object Prioritization means aiming can now prioritize highlighted actions when multiple are possible. So when you are stuck in a Deadlock GravNet next to a rope, you have more control over what you interact with first.
Why does that matter? Because in a clutch round, the difference between grabbing a rope and getting pulled into the wrong animation can decide the fight. It is not a flashy change, but it is the kind of polish that makes the game feel more predictable.
🗺️ Maps and agents touched by 11.09
| Category | Entries |
|---|---|
| Maps | Pearl, Breeze, Abyss, Corrode |
| Agents | Astra, Gekko, Gekko and Killjoy, Iso, Omen, Reyna, Skye, Sage, Veto, Viper, Vyse, Yoru |
🐛 Agent fixes worth knowing
Veto received a cluster of fixes. Riot fixed an issue where the radius indicator when placing the Crosscut vortex would not match the placed one. It softened the visual effects during Veto's Evolution transformation and fixed some bright spots flickering in Agent Select. It also fixed an issue where Veto's Crosscut and Chokehold ability descriptions were inconsistent with their in-game behavior, fixed the tendrils' exit animation on Chokehold that was not showing up, and fixed a bug where using Veto's Evolution would sometimes not count toward weekly mission progress.
Viper also got attention. Riot fixed a bug that caused Viper's Viper Pit to linger in front of you when unequipped without casting, and a bug where Viper's Snake Bite visual effects did not fade at the same time for allies and enemies.
Yoru players should be happy too. Riot fixed a bug where Yoru's Fakeout did not collide with things in the game as if it were a player, and a bug where Fakeout was not being destroyed by abilities it took lethal damage from.
Finally, multiple agents received shared fixes. Riot fixed an issue where audio timing for Suppress audio did not end when the Suppress duration actually ended, and a bug that caused Concuss visual effects to show through thin walls and doors.
🎯 My take heading into 2026
I think 11.09 is a perfect example of Riot doing two things at once: swinging a hammer at abuse and sanding down everyday friction. MFA will not stop every smurf, and it will not fix every ranked complaint. But it raises the cost of account sharing, and that is a meaningful step. The object prioritization changes are the kind of quiet improvement I notice most when I am trying to make a fast play and the game actually does what I intended.
Will the Ascendant+ MFA requirement in 11.10 be enough to clean up high-rank Competitive? That is the question I will be asking all year. For now, I am glad Riot is treating smurfing as Rank Manipulation and giving players a clearer way to report it. 🎮
This discussion is informed by GamesIndustry.biz, a widely cited source for game business reporting and developer-focused analysis. In the context of Valorant’s 11.09 MFA rollout, that broader industry lens helps explain why anti-abuse systems matter beyond player frustration alone: stronger account security can reduce account sharing incentives, support competitive integrity, and reinforce long-term trust in ranked ecosystems where smurfing and boosting directly affect retention.