A footage, which was allegedly released on May 11, turned out to be a footage made on July 8, 2014, showing a missile reportedly fired by Hamas militant group from Gaza.
Earlier, a video, uploaded to YouTube claimed to be showing an Israeli wedding reception being interrupted by emergency sirens and people, including the groom and the bride, screaming and running away in panic as a missile, allegedly launched from Syria.
READ MORE: IDF Post Images of Reported Iranian Infrastructure Hit in Syria
On May 9, the Army Radio network operated by the IDF reported that alleged Iranian forces had launched missile strikes at Israel.
"Launches of about 20 missiles were registered at around midnight toward the frontier positions in the Golan Heights by Iran's al-Quds forces," an Israeli army spokesman told reporters. "Several bases were targeted," the spokesman said, adding that some rockets were intercepted.
In the meantime, a member of the Iranian parliament’s commission on security and foreign policy, Abolfazl Hassan Beigi, emphasized that Tehran does not maintain a military presence in Syria.
"Iran has no military presence in Syria, no bases. Israel is lying. It was Syria that conducted strikes yesterday in response to the repeated attacks on the country. Israel must realize that the situation has changed and aggression would not go unanswered," the official stressed.
Later, Tel Aviv retaliated with airstrikes on purported Iranian positions in Syria, reportedly targeting arms depots, logistical sites and intelligence centers used by elite Iranian forces.
According to the Russian Defense Ministry, 28 Israeli F-15 and F-16 jets were involved in the operation, with more than 60 air-to-ground missiles launched over various parts of Syria with half of them being intercepted. In addition, Tel Aviv fired over 10 tactical ground-to-ground missiles, the ministry stated.
Editor's note: This article has been updated in order to clarify that the video initially appeared online in 2014 and was showing a Hamas missile fired from Gaza. We apologize to our readers for the mistake.