EastEnders fans have predicted that Walford is about to get seriously dangerous with not one, but TWO killers living in Albert Square...
Last night's EastEnders saw Ian Beale find out that killer son Bobby Beale is set to be released from jail in June this year - and fans have gone into overdrive trying to work out who could be next on the murderer's hit list.
Ian spent most of last night's episode hiding the letter from his son's Youth Offending Team, telling him that they would like to organise a home visit before Bobby's release in June.
His date with Jean then ended in disaster after he spent the whole lunch at The Vic distracted. While he wanted to talk about his family and kids, Jean was more concerned about the fact she was having hot sweats.
But when Ian pointed out that it was probably just the menopause, his observation didn't go down well and Jean left... leaving Ian to look at this letter once again.
But with the news that Bobby will soon be free, fans took to social media to reveal that they thought he would soon kill again, and the most likely victim seems to be Hunter...
But not everyone seemed to think Hunter and Bobby would be enemies.
Some fans think that because they've both killed someone, they might have some common ground and could even team up...
But with the net closing in on Hunter, could he still be in Walford by the time Bobby comes home?
Last night saw him dig up Ray's dead body to get the bullet out of his rotting corpse - all in an attempt to get rid of any link to his death and the gun he and Mel still have in their house.
Has Hunter really got rid of the last bit of evidence linking him to Ray's murder? Or has disturbing the body just made it all the easier to find?
EastEnders airs Monday and Friday at 8pm and Tuesday and Thursday at 7.30pm on BBC One.
Picture credits: BBC and BBC / Jack Barnes
Get the latest updates, reviews and unmissable series to watch and more!
Thank you for signing up to Whattowatch. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.