Please welcome our new employee in sub-basement 2-C. He specializes in “free unsolicited offensive security assessments,” focusing on the russian propaganda sector.
Our NSA handlers already warned him about skating in the server room. We expect his compliance going forward.
NAFO Security Operations Center retweeted
The more Trump sells out Ukraine, the worse it gets for @GOP.
And despite losing their party, Republicans STILL refuse to stand up to a completely compromised president selling America and its allies to a hostile foreign regime.
This will never be lived down.
NAFO Security Operations Center retweeted
Ukrainian attack drones hit a datacenter belonging to the Russian social media giant VK tonight, setting it on fire.
VK's network has begun experiencing disruptions.
NAFO Security Operations Center retweeted
🔥 BREAKING
Saint Petersburg's oil loading port has been hit. New footage shows a huge black plume climbing over the high-rises, with the night sky glowing orange-red from below.
A second video shows a fireball near the shoreline. The flames and smoke hang over the water, and the fire is reflected in the river as residential towers stand in the frame.
Russia's supposedly safe, far-from-the-front city now has a burning fuel terminal in full view of its apartment blocks. Fuel for the army is going up in smoke.
Source: @exilenova_plus
NAFO Security Operations Center retweeted
❗️❗️BREAKING: Ukrainian Defense Forces struck the Surgut Condensate Stabilization Plant in Russia’s Khanty-Mansiysk region, roughly 2,400 km from Ukraine’s border. The Gazprom facility processes gas condensate and produces motor and aviation fuel, with capacity of 12 million tonnes a year. #Russia
NAFO Security Operations Center retweeted
The Administration’s decision to reduce intel sharing to Ukraine & access to Starlink equates to aiding the invader & the war criminal who bombs cities. Does the Administration think it will get ANY support for the remainder of the 119th Congress? Their agenda is dead unless they change paths.
nytimes.com/2026/10/14/world…
NAFO Security Operations Center retweeted
🛰️New high-resolution satellite imagery shows the aftermath of Ukraine’s Neptune missile strike on Borisoglebsk airbase in Russia’s Voronezh region.
The wreckage of two destroyed Russian Su-34 fighter-bombers is clearly visible.
Two additional aircraft parking bays in the middle show extensive burn damage, but the wreckage appears to have already been partially cleared by Russian personnel, with debris pushed into piles.
According to Zelensky, four Su-34s were destroyed and two more damaged in the strike.
Last night, Ukraine’s Defense Forces struck an airfield in the Voronezh region. Four Su-34 aircraft were destroyed and two more Su-34s were hit. The Russians used them to terrorize our people. These very warplanes were ready to launch new attacks on Ukraine and were loaded with aerial bombs.
Our Long Neptune missile was used to strike the target. I thank the warriors of the Ukrainian Navy for their precision!
Our long-range sanctions also reached a site in the Oryol region used to store and launch attack drones. A target was also hit in the Black Sea.
These are our justified responses to all of Russia’s terror against Ukraine. Russia is dragging out the war, so our long-range operations will continue.
NAFO Security Operations Center retweeted
No, a Yandex cloud malfunction did not take down disinformation/troll bots. It's a dangerous misconception. This is not how it works, not even technically. After Ukrainian drones hit Yandex data centers, a viral chart showed Russian "bot traffic" collapsing. But those bots are mostly Yandex's own search crawlers, not the info-ops social media accounts. Troll farms hide behind proxies, hijacked devices and Western clouds. They're still operating. Hired influencers are also still around. The "bots went silent" story is misinformation. Believing it is plainly dangerous. It tells people the threat is gone while influence operations keep going. Ahead of elections that complacency is what they may count on.
NAFO Security Operations Center retweeted
I'm sorry to burst everyone's bubble, but as of now, there is no solid evidence that Russian bot farms have become inactive due to the Yandex data centre strikes.
The Cloudflare charts mostly show activity related to web crawlers, which have little to do with automated posting on social media platforms.
This doesn't mean the strikes haven't had an effect, but no one has demonstrated it with solid data so far. Many users have reported seeing fewer pro-Kremlin posts and replies since the strikes, and some automated pro-Russian and pro-MAGA accounts have reportedly gone silent. But this could simply be a coincidence.
Nevertheless, the attacks on Russian data centres have extremely high strategic value for Ukraine, as they can massively disrupt the everyday lives of ordinary Russians.
NAFO Security Operations Center retweeted
Crawlers are a normal part of the web. Yandex runs a search engine; of course it generates bot traffic.
Bot traffic from Russia does not automatically mean Russian propaganda bots. Yet people here, including journalists, keep treating the two as interchangeable.
That Cloudflare chart shows automated web requests from Yandex’s network. Where’s the data showing that propaganda accounts stopped posting?
Journalists in particular need to understand this distinction. Precision matters when a misread traffic graph becomes the basis for a political narrative.
NAFO Security Operations Center retweeted
Air defense has engaged over Moscow. There is currently an air raid alert there.
NAFO Security Operations Center retweeted
Tighten sanctions, not loosen them.
⚡️Russia demands that the USA lift sanctions as part of negotiations on an energy ceasefire with Ukraine and a ceasefire in the Black Sea, — The Kyiv Independent.
👉 Follow @blyskavka_ua
NAFO Security Operations Center retweeted
Yandex Cloud is reporting an open power-failure incident in zone ru-central1-b, starting roughly 2 hours ago.
NAFO Security Operations Center retweeted
Ukrainian attack drones hit Russia's Sasta machine-tool plant tonight, colocated with a major datacenter belonging to the Russian internet giant Yandex.
Multiple explosions and a large fire were reported at the complex in Ryazan Oblast.
NAFO Security Operations Center retweeted
🚨 𝗥𝗨𝗦𝗦𝗜𝗔’𝗦 𝗣𝗟𝗔𝗚𝗨𝗘 𝗘𝗫𝗣𝗟𝗔𝗡𝗔𝗧𝗜𝗢𝗡 𝗟𝗢𝗢𝗞𝗦 𝗠𝗢𝗥𝗘 𝗟𝗜𝗞𝗘 𝗔 𝗖𝗛𝗘𝗥𝗡𝗢𝗕𝗬𝗟-𝗦𝗧𝗬𝗟𝗘 𝗖𝗢𝗩𝗘𝗥-𝗨𝗣
A laboratory worker at Russia’s Irkutsk Anti-Plague Research Institute told hospital staff she had broken a tube containing the plague pathogen at work on 25 September. Within a week she was dead of severe pneumonia. Reporting described a positive plague test and a second test confirming the diagnosis.
Authorities isolated nearly 200 contacts under FSB escort and imposed hospital restrictions. The subsequent federal statement left the cause of her illness undetermined while announcing that microorganisms associated with her work had not been detected and that investigators had found no laboratory accident.
Darya Shipilova, 28, worked at an institute that handles plague pathogens. Reporting also identifies her as a coauthor of research into the susceptibility of Yersinia pestis to antibiotics. The occupational connection is concrete.
Essential Chronology:
25 September: According to the exposure account reported by Pavel Stepanov and Mash and relayed by People of Baikal, Shipilova broke a tube containing the plague pathogen at the institute.
29 September: Shipilova was reportedly hospitalized at Shelekhov District Hospital with severe pneumonia.
1 October: Before any official statement, FSB personnel were accompanying ambulances carrying Shipilova’s contacts to medical facilities for examination. Shelekhov District Hospital introduced quarantine restrictions, suspending admissions and discharges.
Night of 1 to 2 October: Shipilova died in hospital.
2 October: Rospotrebnadzor chief Anna Popova was on the ground in Irkutsk.
2 October, 14:27 MSK: NEWS.ru, citing Telegram channel 112, reported that an initial laboratory test was positive for plague and that repeat testing confirmed the diagnosis. The chronology indicates both tests occurred between 29 September and 1 October (inferred).
2 October: Reporting put identified contacts at 197, with 189 hospitalized for observation and preventive measures. Governor Igor Kobzev described a suspected particularly dangerous infection and a commission meeting with Popova.
2 October: Buryatia’s governor, Alexei Tsydenov, rejected reports that Shipilova had visited his republic. His initial wording described a woman who had died of plague. He subsequently added “possibly.” People of Baikal documented that change.
2 October: REN TV removed five plague-related Telegram posts, including reporting about hospitalized contacts.
3 October: Baykalsk authorities urged residents to limit travel to Shelekhov, citing unofficial information about a human plague case, then deleted the warning less than two hours later.
4 October: Reports described additional hospital restrictions in Irkutsk. At 12:55 MSK, Interfax reported that
4 October: Rospotrebnadzor was describing Shipilova’s illness as “pneumonia of undetermined etiology” and stated that expanded testing had detected “no microorganisms associated with her professional activity.” Rospotrebnadzor also announced a stable epidemiological situation and no identified accident involving pathogenic microorganisms at the institute.
Rospotrebnadzor’s statement fails on its own terms, before any earlier report of positive tests is considered. “Pneumonia of undetermined etiology” is a clinical diagnosis, not a laboratory result identifying the cause. It names the condition while admitting that its cause remains unknown.
The plural “microorganisms” matters. This is a broad statement about occupational pathogens, not simply a negative plague test. The agency has announced non-detection across an unspecified group of work-related organisms without disclosing the testing panel, methods, specimens or collection times.
Those undisclosed negative findings do not establish that her illness was unrelated to the laboratory. A negative result establishes non-detection, not absolute absence. U.S. CDC guidance explicitly recognizes that plague can remain suspected after negative cultures and recommends additional testing. WHO recognizes that poor sampling or prior antibiotic use can produce false-negative cultures.
The exposure account comes from the employee herself, a trained laboratory diagnostician at the institute, and from independent outlets and security-linked channels that rarely agree with each other. The only denial comes from the agency that operates the institute.
The agency is also not a neutral party. The body that cleared the institute is its parent organization. And an agency whose institute specializes in this pathogen reports that it cannot determine what killed that institute’s employee.
Disclosure would close the question: which tests were run, on which specimens, collected when relative to antibiotic treatment, and what the autopsy found. None of that appears in the statement.
The reported positive test makes this worse. NEWS.ru described laboratory identification followed by confirmation. The same day, the governor of Buryatia confirmed that a woman had died of plague. Those results triggered the quarantining of contacts transported under FSB escort, and they are mutually exclusive with the agency’s non-detection claim. Its statement does not acknowledge them.
The state’s conduct does not match its statement. On 1 October, before any official statement, FSB personnel were accompanying ambulances carrying Shipilova’s contacts. On 2 October the head of Rospotrebnadzor traveled to Irkutsk for a commission on what the governor called a suspected particularly dangerous infection. On 4 October, the day the agency announced that no occupational pathogens had been detected, hospital restrictions in Irkutsk expanded. With the cause unknown and the laboratory cleared, those measures have no stated basis.
Public information was handled the same way. Tsydenov’s confirmation was edited to “possibly” in under two hours. REN TV removed its posts, and Baykalsk authorities issued a warning citing a human plague case and withdrew it within two hours.
The containment measures show that authorities treated the incident as a serious infectious threat. The absence of confirmed secondary cases addresses transmission among contacts; it does not settle what caused Shipilova’s illness or where she acquired it.
There is precedent. In 1979 an anthrax release from a military facility in Sverdlovsk was attributed to contaminated meat, and the cause was not acknowledged until 1992. At Chernobyl, Pripyat was evacuated before the state acknowledged the accident. In both cases the measures taken ran ahead of the official account.
That is why Russia’s explanation looks more like a Chernobyl-style cover-up. The analogy concerns the handling of information. Authorities have cleared their own institution of an accidental release of a deadly pathogen while being unable to identify what killed its employee: these findings side by side are unsound given the lack of any supporting evidence.
#OSINT #Russia #Irkutsk #plague #PneumonicPlague #pneumonicplague #russianplague #russiaplague
NAFO Security Operations Center retweeted
Genocide wasn't a strong enough reason to close Europe's borders for Russian tourists, but perhaps we might find the threat of the Black Death unacceptable?
NAFO Security Operations Center retweeted
🔥✈️ Footage from the crash site of a Russian military plane in the Amur Region.
The crashed plane could be Tu-95MS or Il-76. It belonged to Ukrainka air base.
According to updated data, 6 of the 7 crew members have already died.
82%: probability that Alexandra is fully aware that “russia is not my enemy” was a russian bot campaign and is simply amplifying that message.
18%: probability that she is truly naive enough to believe that it was an organic social media campaign.
Which do you believe?






























