top of page

Adam Copeland Spooks Malaki Black With Callback To Notorious WCW Botch On AEW Dynamite

On the May 9th, 2000 episode of "WCW Thunder," a torrent of fake blood descended from the ceiling and proceeded to completely miss Kevin Nash. On last night’s episode of "AEW Dynamite," history repeated itself, as Adam Copeland unleashed the Brood's bloody floodgates onto Malakai Black.


Just moments before his bloody baptism, Malakai Black secured a victory over Kyle O'Reilly to gain momentum going into his Barbed Wire Steel Cage Match at Double Or Nothing for the TNT Championship. Before Malakai Black could rest on his laurels, red and black lights flashed in the ring. Then, gallons of gore spilled onto Malakai Black. As with Kevin Nash, the rush of viscera initially missed the challenger, landing slightly behind him, but unlike Kevin Nash, who simply stared in disbelief, Malakai Black not one known for shying away from the disturbing fell flat to roll in his crimson bath. Adam Copeland then appeared on the video screen to taunt his opponent, telling Malakai Black he should be careful what he wished for.


Adam Copeland's revenge follows last week's events, which saw the House of Black blindside, assault, and humiliate Adam Copeland by removing his wedding band. It seems that Adam Copeland intends to revive a version of his vampiric Brood-era persona to meet Malakai Black's levels of gothic depravity, and Malakai Black's bloodbath was the TNT Champion's way of simultaneously intimidating and humiliating his future opponent. Fans have also speculated that the segment could herald the involvement of former Brood leader Gangrel, an idea Adam Copeland pitched before leaving WWE.


As of this writing, Adam Copeland has held the TNT Championship for 63 days and counting. His Double or Nothing match with Malakai Black will mark Adam Copeland's fifth televised title defence.


Photo Credit: AEW


Need more Real Rasslin? linktr.ee/realrasslinuk


Wanna work with us? Drop us a DM!

Comments

Rated 0 out of 5 stars.
Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page