Star Trek writers and Tom Cruise resurrect Van Helsing

May 02 // Xander Markham

Universal have announced that two characters from their roster of classic monster movies will be making a comeback with the assistance of Tom Cruise and Star Trek writers Alex Kurtzman and Robert Orci. Cruise will take the starring role in a reimagining of Van Helsing, a character most recently portrayed by Hugh Jackman in a messy 2004 attempt at franchise building. The Mummy will also be returning (I hope you read that in a sufficiently ominous voice), although there's no mention whether it will be in any way related to the Brendan Fraser movies or Dwayne Johnson Scorpion King spin-offs.

I'm always keen on a new monster movie, but recent efforts have consistently disappointed: The Mummy movies were pretty abject after a decent first entry, the aforementioned Van Helsing struggled to bring life to an inspired premise (multi-monster mashup), and 2010's The Wolfman had a troubled production history and wasted a cast as talented as Benicio Del Toro, Emily Blunt and Anthony Hopkins. Kurtzman and Orci also wrote Transformers 2, so that's not exactly reassuring. Fingers crossed though!

[via Coming Soon]


 BLOG A RESPONSE



Xander Markham // Associate Editor
 Follow Blog + disclosure Tips
Living just outside London, I represent Flixist’s entire UK branch. My film obsession manifested itself during a childhood spent watching Bond movies, Italian Westerns and all things samurai. I... full profile | More staff profiles

Get more Flixist:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.

advertisement:

138 PEOPLE ARE READING:



Back to Top