Gigi Hadid shuts down YouTuber Jake Paul for dissing Zayn Malik

It didn't take long for Gigi to defend her man after Jake threatened to 'clap' him


Entertainment Desk February 24, 2020
Photo: File

Gigi Hadid is not one to mess with, and the gorgeous model has shown that once again!

Gigi defended her beau Zayn Malik from YouTuber Jake Paul who, on Sunday morning, took Twitter to alleged that he had ran into Zayn at the MGM in Las Vegas and he had been rude to him.

"Almost had to clap up zane from 1 direction because he is a little guy and has an attitude and basically told me to f--k off for no reason when I was being nice to him," Jake said in a tweet that he has since deleted.

It didn't take Gigi long to jump to her man's defense as she launched a tirade in reply to Jake who had ended his tweet with, "Zane I know you're reading this... Stop being angry cause you came home alone to your big ass hotel room."

"Lol, because he doesn’t care to hang with you and your embarrassing crew of YouTube groupies?" wrote Gigi.

https://twitter.com/GiGiHadid/status/1231560100437012480

She continued saying, "Home alone with his best friends like a respectful king cause he has me, sweetie." Talk about a power duo!

Naturally, Twitter exploded, lauding Gigi for taking a stand against Jake, who isn't exactly popular with fans on Twitter.





https://twitter.com/pourmercyonlwt/status/1231570369347280896

Jake then proceeded to delete his tweets and later tried to remedy the damage that had been done. "Someone needs to take my phone when I’m drunk," he wrote, attempting to imply that he was under the influence and did not mean to tweet what he did.



Zayn, however, remained mum through the entire exchange, in typical Zayn fashion.

Gigi and Zayn rekindled their on-again, off-again romance late last year and have always stuck up for each other.

Have something to add to the story? Share it in the comments below

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ