FANDOM


Spider Man 2 Quote1This has got to be the worst alternate universe ever.Quote2 -Spider-Man

Hey! Article is a stub. This means that it is short and needs more information, or should be expanded with up to date information, if there is any new information. You can help the Spider-Man Wiki by expanding it. Thanks!
Remember users, remove this template ONLY if the article has been expanded enough.


Scarlet Spider Vol 2 24
"Hands Covered in Blood: Part 1 of 2"
Comic Book series: Scarlet Spider Vol. 2
Issue Number: 24

First published:

November 27, 2013

Executive Editor:

Alex Alonso

Cover Artist:

Ryan Stegman

Writer(s):

Christopher Yost, Erik Burnham

Penciler(s):

Carlo Barberi

Inker(s):

David Baldeon

Editor(s):

Tom Brennan

Previous issue:

Scarlet Spider Vol. 2 #23

Next issue:

Scarlet Spider Vol. 2 #25

"... He's right. Everything he said, everything Kraven said... It's true. I fought super heroes... I killed people. For money... I even killed people I thought I loved."
— Kaine


Scarlet Spider Vol. 2 #24 is the 24th issue of Scarlet Spider Vol. 2.

Solicit SynopsisEdit

  • The stunning aftermath of Into the Grave has arrived!
  • His encounter with Kraven the Hunter forced the Scarlet Spider to make some immense sacrifices. Now Kaine has to make a choice…one that may see him leaving his new life forever.
  • Chris Yost, Erik Burnham and Carlo Barberi bring you the decisive moment in the life of The Scarlet Spider!

AppearancesEdit

Featured Characters:Edit

  • Kaine (appears in main story and flashback)

Supporting Characters:Edit

Villains:Edit

Other Characters:Edit

Locations:Edit

  • Texas
    • Houston
      • Church
      • Park Plaza Hospital
      • Four Seasons Hotel
    • The Houston Zoo (appears in main story and flashback)

Items:Edit

Vehicles:Edit

  • Taxi

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.