Disinfo: Rumours of the existence of secret protocols to the Molotov–Ribbentrop Pact appeared soon after the pact was signed, but the originals of these “secret additions” have not been found still today

Rumours of the existence of secret protocols to the Molotov–Ribbentrop Pact appeared soon after the pact was signed, but the originals of these “secret additions” have not been found still today.

Recurring disinformation and historical revisionism. The article does mention that in 1989, the Soviet Congress of People's Deputies "condemned these protocols", but fails to state that it also confirmed that the secret protocols were authentic. https://www.lawmix.ru/docs_cccp/1241 The original documents were burned by the Nazis at the end of the war, but a microfilm copy was saved and turned over to British and American authorities, who revealed its contents. For more, read https://www.nytimes.com/1989/12/25/world/upheaval-east-soviet-congress-condemns-39-pact-that-led-annexation-baltics.html The German-Soviet Nonaggression Pact was concluded before the beginning of World War II and divided eastern Europe into German and Soviet spheres of influence. To the public pact of nonaggression was appended a secret protocol, which divided the whole of eastern Europe into German and Soviet spheres of influence. Poland east of the line formed by the Narew, Vistula, and San rivers would fall under the Soviet sphere of influence. The protocol also assigned Lithuania, Latvia, Estonia, and Finland to the Soviet sphere of influence. www.britannica.com/event/German-Soviet-Nonaggression-Pact,


  • Reported in: Issue 118
  • DATE OF PUBLICATION: 21/08/2018
  • Language/target audience: Russian
  • Country: USSR, Russia, Germany
  • Keywords: Historical revisionism, WWII


Cases in the EUvsDisinfo database focus on messages in the international information space that are identified as providing a partial, distorted, or false depiction of reality and spread key pro-Kremlin messages. This does not necessarily imply, however, that a given outlet is linked to the Kremlin or editorially pro-Kremlin, or that it has intentionally sought to disinform. EUvsDisinfo publications do not represent an official EU position, as the information and opinions expressed are based on media reporting and analysis of the East Stratcom Task Force.

see more

MH17: JIT used fake video to show the missile had come from Russia

Joint Investigation Team on the downing of flight MH17 used doctored footage of a Buk missile being transported on a white truck in order to show that the missile came from Russia, said Nikolai Parshin, chief of the Russian Defense Ministry Main Rocket and Artillery Directorate.

On the video provided by JIT, the images of the truck and “Buk” are collated on the image of a street section. We see that “the right section on the truck’s surface is painted white, while the whole car is in the shadow”, said Parshin.

Also, according to the Russian Defense Ministry, the truck carring Buk missile is moving in the wrong direction in the JIT video.


Bellingcat says Russian defense officials have misinterpreted shadows and objects in an attempt to show there was a problem with lighting in videos produced by the Joint Investigation Team.

The Russian side uses images to claim the white part of the cabin of the truck, which, according to the JIT's conclusions, transported a Buk missile system from Russia to Russian-occupied Donbas, shouldn't be visible in shadows. The Buk was used by Russian-led forced to shoot down a Malaysia Airlines Boeing. "…We see the white part of the top of the cabin turns black when it enters the shadow, but the top right part doesn't. But this is based on the idea the top of the truck that goes dark is white, but it's not. It's a dark band that's reflecting sunlight making it look white in the low quality footage, and without the reflecting light, it's much darker," Eliot Higgins, founder of Bellingcat explains. Read more on Unian: https://www.unian.info/world/10264413-bellingcat-founder-russians-misinterpret-shadows-and-objects-in-jit-s-mh17-related-videos.html

Regarding the wrong direction of the truck, Higgins notes that the Russian MoD is correct in saying it's moving in the wrong direction in the JIT animation, but this does not serve as evidence that

one of the photographs is fake, as the location the photograph was actually taken is different. "The camera was facing south, and the Buk is pointing east, which means it's actually travelling in the correct direction, just the JIT animation was wrong. The Russian MoD uses this to falsely claim the photo is fake".

Further debunk by The Insider.


Ukraine didn’t provide information for the investigation of MH17

Ukraine did not provide information for the investigation into the downing of Malaysian Airlines flight MH17, which indirectly proves its guilt, said Nikolai Parshin, chief of the Russian Defense Ministry Main Rocket and Artillery Directorate.


"In the JIT Australia, Belgium, Ukraine, Malaysia and the Netherlands are working together," said the JIT itself in its most recent statement: https://www.om.nl/onderwerpen/mh17-crash/@103196/update-criminal-0/

According to The Insider, Ukraine was fully cooperating with the Joint Investigation Team. Moscow claimed that the JIT ignored evidence provided by Russia and, for that reason, it has refused to cooperate with the investigation.

It was a Ukrainian regiment that shot down MH17

The missile that shot down MH17 came from an the Ukrainian missile regiment, said Nikolai Parshin, chief of the Russian Defense Ministry Main Rocket and Artillery Directorate. According to Parshin, this Ukrainian military unit is now called the 223rd anti-aircraft defense regiment of the Ukrainian armed forces, was renamed by a decree from the Ukraine presidential office. “Currently, this unit is located in the city of Stryi in the Lviv region, [and] they still have the Buk systems. It is noteworthy that units of the 223 regiment have, since 2014, repeatedly been involved in the so-called anti-terror operation in the Donetsk and Lugansk regions.”, he added.


Bellingcat has identified that on the photos in VKontakte of an Ukrainian volunteer, it's evident that the 223rd Stryi Missile Regiment was in 2014 in the Poltava region. "The Poltava region is central Ukraine. Missile's range would be" too short, says Kirill Mihailov, researcher at Conflict Intelligence Team. "The only operational Buk missile launcher observed within firing range of MH17 on July 17, 2014, was the Russian Buk 332, from the Kursk-based 53rd Anti-Aircraft Missile Brigade," a surface-to-air combat unit of the Russian ground forces that was stationed in eastern Ukraine at the time, Bellingcat reported. Further debunk by The Insider. Background: Many competing and contradictory stories promulgated by Russian state-controlled media on MH17. https://euvsdisinfo.eu/disinformation-cases/?text=mh17&disinfo_issue=&date= The Dutch-led Joint Investigation Team has concluded that flight MH17 was shot down on 17 July 2014 by a missile of the 9M38 series, launched by a BUK-TELAR, from farmland in the vicinity of Pervomaiskiy (or: Pervomaiskyi). At that time, the area was controlled by pro-Russian fighters. The BUK-TELAR was brought in from the territory of the Russian Federation and subsequently, after having shot down flight MH-17, was taken back to the Russian Federation. https://www.om.nl/onderwerpen/mh17-crash/@96068/jit-flight-mh17-shot/

24 May 2018, JIT stated that the BUK-TELAR that was used to down MH17 originates from the 53rd Anti Aircraft Missile brigade, a unit of the Russian army from Kursk in the Russian Federation. The JIT reached this conclusion after extensive comparative research. Several images of the BUK-TELAR with which MH17 was downed are available. Analysis of those produces a number of characteristics. The combination of those is so special that that can be considered as a fingerprint. This fingerprint has been compared with numerous images of BUK-TELARS, both Ukrainian and Russian ones. The only BUK-TELAR on which this combination of characteristics also was found, is a BUK-TELAR that was recorded several times when it joined a convoy of the 53rd brigade on 23 – 25 June 2014. https://www.om.nl/onderwerpen/mh17-crash/@103196/update-criminal-0/ Furthermore, a joint international open source investigation led by Bellingcat has identified conclusively that the person of interest known as ‘Andrey Ivanovich’ or ‘Orion’ whose identity is sought by the Joint Investigating Team in connection with the criminal investigation into the downing of MH17, is in fact Russian citizen Oleg Vladimirovich Ivannikov. Ivannikov was an officer of the Main Directorate of the General Staff of the Russian Ministry of Defence (GRU), and served in that function until at least as late as September 2017. During his undercover deployment to LNR, he coordinated and supervised the military activities of Russian militants, pro-Russian separatists and “private army” contingents from the Wagner group. Ivannikov also supervised the procurement and transport of weapons across the Russia Ukraine border. He held these functions at the time of the downing of MH17. https://www.bellingcat.com/news/uk-and-europe/2018/05/25/mh17-russian-gru-commander-orion-identified-oleg-ivannikov/ The European Union an NATO have called on the Russian Federation to accept its responsibility and to fully cooperate with all efforts to establish accountability http://www.consilium.europa.eu/en/press/press-releases/2018/05/25/declaration-by-the-high-representative-on-behalf-of-the-eu-on-the-findings-of-the-joint-investigation-team-on-the-downing-of-flight-mh17/ https://www.nato.int/cps/en/natohq/news_154585.htm On the basis of the JIT’s conclusions, the Netherlands and Australia are convinced that Russia is responsible for the deployment of the Buk installation that was used to down MH17. The two governments are formally holding Russia accountable. https://www.government.nl/latest/news/2018/05/25/mh17-the-netherlands-and-australia-hold-russia-responsible The US have supported the decisions by the Netherlands and Australia https://twitter.com/statedeptspox/status/1000039780384755712