Warning: there are potentially MAJOR SPOILERS for Doctor Strange ahead! If you don't want to know what happens in the movie, turn away now and click on another one of our fine articles.
Thanks to the internet and social media, it's easier than ever for movie spoilers to come out, and not just in terms of information coming out right after a movie hits theaters. Doctor Strange is still three weeks away from being released to the masses, and already the movies two end credits scenes have made their way online. By the Vishanti!
While we can't say with 100% certainty that these are legitimately the Doctor Strange end credits scenes (provided by Screen Crush), they certainly sound interesting enough, and they also potentially set the stage for things to come elsewhere in the Marvel Cinematic Universe. With that in mind, let's dive into what supposedly will happen in these two scenes.
I'll give one more chance for those of you who don't want to be spoiled to exit the premises...are we all good? Okay, let's dive in.
The Mid-Credits Scene
After defeating his adversaries in the main Doctor Strange story, Stephen Strange has now made it his priority to rid our world of mystical threats, and that includes a notorious trickster from Asgard. However, he decides to recruit some help dealing with this particular problem: Thor. Back at the Sanctum Sanctorum, Stephen Strange meets with the God of Thunder to learn about Loki, but Thor then says he needs help finding his adoptive brother to find Odin, who is still missing following the events of Thor: The Dark World. Strange agrees, but one one condition: once Thor finds Loki and Odin, all of them must leave Earth and never return, setting the stage for Thor: Ragnarok. Evidently the Master of Mystic Arts doesn't want any otherworldly individuals getting involved in Earth's affairs, whether they're good or bad.
Most of you will remember that in Thor: The Dark World, Loki faked his death and later impersonated Odin so he could take the Asgardian throne for himself. Evidently Thor now knows his brother is still alive and needs help finding their father. While Thor would obviously want his dear ol' dad back safe and sound, one would wonder if he also needs Odin's help against the evil forces at work next year in Thor: Ragnarok. It's also worth noting that back in August during Thor: Ragnarok's shoot, Chris Hemsworth was seen holding a business card that had the address for the Sanctum Sanctorum on it on a set made to look like New York City, so this isn't the first time a connection between Doctor Strange and the Thor world has been formed.
Head to the next page to find out what the Doctor Strange post-credits scene may have to offer!
The Post-Credits Scene
The Infiltrator's Benjamin Bratt was one of the later additions to the Doctor Strange cast (at least publicly), but his character hasn't been revealed. Well, according to this report, he is a mystical healer that worked his magic (see what I did there?) to fix his paralysis. In the post-credits scene, we reunite with this healer again when Mordo approaches him. Although an ally for most of the movie, Mordo is now angry that Stephen Strange was named the Sorcerer Supreme by The Ancient One, and he's decided to cross over to the dark side. As a result, he kills Benjamin Bratt's character and steals his powers, saying "There are too many sorcerers."
Given Baron Mordo's villainous history in the comic books, it wasn't so much a question of if he would become evil in the MCU, but when. As for when we'll see him as full-blown super villain, that's hard to say. A Doctor Strange sequel is obviously the best bet, but there's also a chance he could appear in another movie, too. Either way, Mordo looks like he's gearing up be an even bigger player in this universe.
Connoisseur of Marvel, DC, Star Wars, John Wick, MonsterVerse and Doctor Who lore. He's aware he looks like Harry Potter and Clark Kent.
Your Daily Blend of Entertainment News
Thank you for signing up to CinemaBlend. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.