Venom is a success at the box office and finally, Sony will be looking forward to other Marvel Characters film under their banner. Morbius, starring Jared Leto is next on the list. Not much has been revealed about it yet, other than Leto’s involvement in the film. However, it was announced today that the film’s villain has been revealed.

This comes via a new report by That Hashtag Show, revealing that a villain named Loxias Crown will be seen squaring off against Leto’s Morbius in the film. This has confused many fans as the Morbius comics had no such character in their issues. However, THS links him to another Marvel character, who goes by Crown.

According to the report, the character will be altered from his original story from the comics. He will reportedly suffer from the same disease as Morbius in the film. Both will be given the same serum to cure them, but they will attend their powers pretty differently. This will turn Crown into a blood-thirsty villain while Leto’s character will stop him.

Venom producers Avi Arad and Matt Tolmach will return to produce the film which is being directed by Daniel Espinosa.

While many fans speculate that Morbius will be connected to Venom in some way, Matt Tolmach explained that this won’t be the case.

“I don’t think there’s a rule written somewhere in stone that all of them have to be one thing,” Tolmach shared. “I think we’ve all talked about, ‘Well, if one of these presents itself in a way…’ Look, we have all seen, as you’ve said, the R-rated versions of these movies now working. So, that’s out there. You can succeed to a staggering degree.”

Facebook comments:

Leave a Reply

Adcodes and Instructions provided for: animatedtimes.com ============================================== animatedtimes.com ============================================== ======================================== SID 15564 EDGE_Animatedtimes.com ======================================== PLACE THIS CODE BEFORE THE TAG Edge Ad Code: EDGE_Animatedtimes.com ======================================== ======================================== ***EDGE Trafficking Instructions:*** ======================================== EDGE ad code should be placed directly on the site within the body at the end of the page. The default EDGE configuration is described below. If you have requested a custom configuration, please disregard default settings below. EDGE can be trafficked through ad servers via javascript tags, 1x1 javascript pixel, or DFP/GPT synchronous tag. In DFP, make sure that SafeFrame is disabled (it is automatically enabled by default), otherwise the tags will not work properly. For DFP/GPT, see this link to "Traffic and serve out-of-page creatives": https://support.google.com/dfp_premium/answer/1154352?hl=en ======================================== ======================================== ***EDGE Default Configuration:*** ======================================== SLIDER - Rails w/ Content Detect and Footer w/ Ad Detect: - Serve rail placements (160x600, 300x250 and 300x600) for Desktop when open space is available. All sizes are located at the bottom of the window by default. - When rail space is not available, serve 728x90 or 970x90 footer. With Ad Detect enabled for desktop footers, a 728x90 or 970x90 will not be served when it covers a standard IAB format (728x90, 300x250, 160x600, and/or 300x600). ======================================== ======================================== ***EDGE Default Settings:*** ======================================== - Device Targeting: Desktop, Tablet, and Mobile Phone - 100/24 Frequency cap - Minimum Time between EDGE sliders: 3 seconds is the minimum time allowed; may be increased ========================================