Intel Update: Nov. 21 - Suddenly, All at Once
People in this report
Places in this report
Orgs in this report
Places in this report (16)
Map data OpenStreetMap contributors · Leaflet · click a pin for entity / search / OSM
Hello again everyone, and welcome back to The Underground. This is the intel update for November 15th through the 21st, 2026. This week, the cyber war continues on, and the war on information has kicked into high gear as well, so let's get right to it. Starting off with the global overview, this week has witnessed a nearly daily cyber incidents, which have mostly turned out to be large scale cyber attacks carried out by a wide array of malign actors. Within Europe, the war in Ukraine has intensified this week as both Ukraine and Russia continue their winter offensive for this year. Meanwhile, the war drags on in the Middle East with no end in sight and escalation always on the menu. So let's go ahead and start with the Middle East for this week. And around the region, a few developments have transpired that are worth being aware of, which have gotten more serious over the past 24 hours. As we await a decision on what the White House intends to do regarding the war, there is the implication that nothing is happening, which is certainly not true. Yesterday, Iran claims to have fired a surface-to-air missile at an American F-16, which appears to have damaged the aircraft. Immediately after the alleged strike, the pilot turned on their transponder and made a very erratic landing in the UAE. In addition to the ADS-B track that we have from public sources, we also have the expected Iranian propaganda report or video, which appears to show a missile detonating near the aircraft. But from the video, it's very hard to determine any kind of context or whether or not the aircraft was damaged. For the record, CENTCOM officially denies that Iran actually hit the aircraft. They're denying the whole thing, as usual. Based on the information that is publicized, it does look like the F-16 probably got clipped or maybe damaged by shrapnel in some way, but was able to make it back to friendly lines, thankfully. Even though this was not a successful shoot-down incident, this incident is a heavy reminder of the stakes of this war. There are real lives on the line here, and even though we're slowing down for the upcoming holiday season here back at home, the potential for a hot shooting war to resume is very high. Otherwise, Iran continues to strike every single convoy of ships that tries to exit the Strait of Hormuz, and they have also been striking American missile defenses and radar sites in Kuwait and Bahrain this week. I don't have any fresh satellite imagery of the region just yet. There have been new passes, but we've got that dreaded cloud cover, so there's not a whole lot I can do about that. This is something that happens throughout the region during the wintertime, so we're just gonna have to work with what we've got, and that's not much. But there are some reports that these strikes wounded American service members. However, as always, that is something that we can never really know unless whistleblowers come forward, as they have in the past, to indicate what the results of these strikes really were. Battle damage assessment, BDA, is gonna be really hard to get on some of these strikes, uh, moving forward, so we're just gonna have to take all of this with a giant grain of salt now. More strategically, after the APEC summit in China, the White House seems rather content to enter into the dreaded forever war phase of the conflict, with neither peace nor full-blown war being the chosen course of action. President Trump himself has stated several times that he has changed his mind after the midterms, and he's not interested in doing anything until after the new year, which might be his way of walking away. However, this could also be either a lie, or he might change his mind by this afternoon. It's impossible to say. One day we're leaning toward war, and the next day we're leaning back toward diplomatic solutions. There is some speculation that the United States is secretly paying Iran a toll fee to get some level of petroleum out of the Strait, which might explain the lack of urgency in making a decision of what to do. This secret toll idea has been floated for a few months now, and it's certainly debatable, but equally debatable are the true raw figures of how much oil is exiting the Strait every day. Since we can no longer trust a lot of the sources that have been historically decently reliable regarding oil flows, we have to wait much longer, maybe upwards of a month or so, in order to get a final, no kidding, checked and rechecked and triple verified account of how many barrels actually made it to the United States. That's the level of information warfare we're dealing with here. We have to really, really, really make sure that we are making decisions based off of information that is not manipulated, and because of the way that the war has been fought, that's really hard to do. This takes time, and right now the White House certainly seems content with the level of oil that's exiting the region, which may be an indicator of either the Iranians getting caught napping and not striking ships that they probably should be striking, or the US is paying the fee to get some level of oil out, even though it may be about half of what's normal. Understandably, most Americans just don't care about the minute details of all of this, and they're really just kind of wondering, "Why is gas so cheap right now?" The answer to that is kind of debatable, but taking a stab at a few possible explanations, it could be that we're paying the toll, uh, or it could be that the Iranians are not striking as many ships as they probably should be. Maybe they've taken their foot off the gas, I don't know. Seasonal demand is also now in play. Uh, demand for gasoline normally goes down in the wintertime, usually at least. So that might be a reason why if you have a fixed supply but your demand comes down, well, price comes down too. So again, basic supply-demand economics, that might be a factor. Also, some prices of some petroleum distillates are actually not coming down. Uh, heating oil, for instance, has come down quite a bit, uh, in the past couple of weeks, sort of like gas prices have, but it's still roughly double the price per gallon that it was before the war. It used to be around $2 a gallon, now it's about four. So that's pretty expensive for all those, uh, up in the northeast who are trying to fill up two or three hundred gallon tanks for the wintertime. That's, uh, a pretty big cost. So in any case, uh, trying to make sense of all of this is rather complicated and also quite fatiguing, uh, as the numbers are probably being cooked on all sides, so we're really never gonna know the full truth. We just kind of have to live with the uncertainty of how all of this is working out so far. What is slightly easier to track are the movements of hardware around the region, such as the strategic movement for this week. As we recall from earlier this week, the USS George Washington carrier strike group has departed CENTCOM, leaving the two other aircraft carriers, the Bush and the Roosevelt, on station in the Arabian Sea. At face value, this is an indicator of some level of de-escalation. However, we don't really know for sure what the deployment schedule really is. Remember, last week, Secretary of the Navy Hong Cao held a town hall meeting in Norfolk with the families of the USS George H.W. Bush, which has been in theater for longer than the Washington has. During that town hall, he directly told the families of the crew that the Bush would be staying out for a full year, and that the US Navy is now going to do full year deployments at sea instead of the six months that used to be standard. Understandably, the families were quite upset at this news and...A mild state of unrest was reported in the auditorium during this town hall, but that direct confirmation from the SECNAV himself was also what heavily indicated that the three carrier posture was going to be the standard in CENTCOM. Also, several Pentagon officials did confirm that the Roosevelt is not replacing anyone, and that the three carrier posture was what they were planning. Well, lo and behold, this week, the Washington was pulled off station to go back to PACOM after about six months of deployment, which is the standard, uh, that carriers normally do. Which makes no sense, as the Bush has been on station for much longer. So clearly, the carrier scheduling is all out of whack, and I don't really know what to make of it. Maybe this is intentional. Uh, maybe they're trying to do a little bit of deception with, uh, their carrier scheduling. Who knows? Maybe the Washington's just gonna go rest, refit, and come right back out again. Who knows? We just don't know. They're not saying. Clearly, some decisions are being made and reversed, or deployment plans are being reworked. It's really, really hard to say what's going on at this point, and I don't think the US Navy itself is even able to plan these things out like they used to. Carrier deployments, just for those who don't know, carrier deployments used to be planned years in advance due to the logistical requirements of keeping a flotilla supplied. Of course, carriers can deploy very, very quickly if need be. We see this with hurricanes all the time. Every season, the Norfolk empties out, 'cause all the carriers put to sea so they don't get, uh, banged up in the harbor there. But when it comes to going to war, that's maybe a little bit of a different issue, and they wanna make sure that there's somebody to replace a carrier that's already in a war zone. As of right now, it's really gonna be hard to say who the replacement for these three carriers is going to be. They might have to send the Lincoln right back out again. I don't know. At this point, it seems like they're really only able to plan these things out a couple of months in, in advance, just due to the rapidly changing nature of the decision-making process. But the general insinuation is that the CENTCOM heavy deployments of naval forces will continue long into the new year. So that's the situation in the Middle East for right now. We're in this kinda purgatory state, where we don't really have a full return to war, but we also don't have peace either, and strategic moves are being made to ensure that enough forces are on station to continue the fighting if that is the chosen course of action. Switching to the homeland for this week, due to the long train of cyber incidents and suspicious happenings, concerns are growing within the homeland that we may be fighting a quiet cyber war against unknown actors far and wide. As always, anything within the digital world is going to be nearly impossible to verify, and for the most part, we have to look at the real world impact to determine what is going on. It would be very, very unwise to attribute all of these incidents to one actor or one particular cause. It's probably the result of a lot of things starting off slowly and then suddenly becoming a problem all at once, as the phrase goes. And suddenly, all at once, we have some problems. So let's run down the list of major cyber incidents that may or may not be cyber attacks which have taken place recently. All of these shenanigans really started back in late October, so we'll kinda start there, because that's when things really started hitting that exponential growth curve. From October 22nd to the 29th, almost a month ago, the European Commission was hacked. This attack resulted in HR networks, such as their, uh, like, internal payroll data and databases being breached. Around the same time, during that same week, the 23rd to the 29th of October, the Amadeus data provider, which is kind of like an analytics company for airline companies, they reported a breach and multiple airlines were hacked, which did affect bookings around that time. Once again, this one was played off as just kind of an IT issue, but now they've actually confessed that it was a cyber attack. On October 29th, we had the Binance hack. This was the major cryptocurrency exchange which was hacked, and $6.3 billion worth of crypto was stolen, which is the largest crypto theft in history. From November 2nd through about November 10th, there were the refrigerator hacks, where refrigerators throughout Europe, mostly in France, were turned up to 11, and all the food was spoiled in hundreds of grocery stores around the continent. Around the same exact time, we only ag- of course, found out about this later, but around the same time, this is also when the commissaries on American military bases in the United States were affected. As part of the same series of hacks, six different US military commissaries were also hit, so that was, uh, kind of all the same sort of incident back on November 2nd through the 10th. Little over a week ago, from November 12th through the 14th, we had the global Microsoft outage, which resulted in everyone who uses Outlook to rejoice that it was actually offline for a while. This one was not a confirmed cyber attack, at least yet. Microsoft is most certainly trying to, uh, avoid that, uh, cyber attack word with this one. But Microsoft products have not really been doing so hot normally, even without malign action this year, so we'll just kinda have to see how that goes. Right during the middle of that, the very next day after that one was, uh, actually announced, November 13th, we had the mass FAA outage, which resulted in the largest ground stop since 9/11. A few days later, on November 16th, we had the United Airlines outage, which was a smaller outage. It was kind of more of a, uh, nuisance sort of thing. This grounded United aircraft for almost two hours, but this was a cyber attack, at least that's what United is saying. On November 17th, the next day, NSANet went down for the NSA. There are conflicting reports on this one. Some say this was a scheduled outage that was actually an- announced in advance, and others are viewing the whole situation with skepticism, saying this might have actually been a cyber attack. Who knows? Taking down NSANet is a very, very, very big deal. It's like taking down the SIPRNet or JWICS, so these systems are extremely classified, and let's just say they're some of the most robust information networks in the country. So this is a very, very serious deal if this was a malign actor. We don't know. We're probably never going to know because of how classified these networks are, so just something to keep in mind with that one. Around the same time, from November 16th through the 19th, we had the JPMorgan Chase breach. Again, this one was initially touted as being a simple IT outage, but JPMorgan actually came back and said, "No, this was a cyber attack," which took the wind out of the sails of all the government officials who said that it was, you know, just a regular IT outage. A little bit later, from November 15th through the 20th, we had the US Department of Agriculture, the USDA, was hacked, which brought down a lot of customer portals, mostly affecting things like insurance payments or grant payments. Really, the payment portals were kind of affected for a lot of users. We do not have a whole lot of informa-Information because we just learned about the USDA hack last night, but just as a reminder, this might not affect only farmers. This might affect a lot more people. If we recall, the USDA is the main federal agency that is in charge, uh, of the administration for things like food stamps and EBT benefits. So one might can read between the lines here and see that if the USDA is getting hacked with their payment systems, theoretically, this is speculation here, but theoretically, it might be possible that there's some impact there, uh, down the line to EBT systems. Once again, EBT benefits, uh, food stamp programs are generally administered by the state. The state normally pays them out, but again, a lot of that money comes from the federal government. So the interface between the feds and the states to disperse these funds, well, that's a little bit concerning, a little bit called into question if the USDA's payment systems are being hacked, right? So something to keep an eye on. I will most certainly very much be watching the USDA over the next few days to see if any of that sort of thing was affected because if so, that could be a lot more serious than just an insurance payout, uh, being delayed for a few days. So moving to this morning, we actually had the disclosure that the FBI was hacked. Turns out the National Crime Information Center was hacked this morning, or at least some time recently, and the FBI's only come clean about it today. This, ladies and gentlemen, once again, quite important. This is the background check service, uh, that whenever you buy a firearm in the United States, they ... You fill out a 4473. They do a background check for you in the store. That's the system that was hacked and customer data was breached because of course it was. So not super great. Once again, this came out literally as I'm recording this this morning, so, uh, we're gonna have to see how that works out. It may be nothing. It may be way more serious than we think it is, but that's just, uh, kind of on the menu at the moment. I'm sure there will probably be another major cyber attack before I'm even done editing this for today. So in addition to all of these major incidents, there are around two to 300 other incidents worthy of note that would honestly just take too long for me to go through individually, but most of the other entities that have been affected this week by cyber attacks, incidents, IT outages, whatever you wanna call them, are police stations and hospitals with cyber attacks taking down 911 dispatch centers and some, uh, police websites like their, uh, non-emergency lines and their, uh, record search websites, things like that, and also hospital administration systems all around the world for things like patient billing and things that are less secure when it comes to the IT systems for hospitals. So both of these are a pretty big concern. It's, it's not just limited to the United States. This is all around the world at this point, but you can see how things are getting pretty serious. Like I said, slowly then suddenly all at once. From a more wave top level, when a lot of very critical systems are failing all around the same time, common sense would dictate, at minimum, we should assume these events are the result of malign action until proven otherwise. Since we are dealing with a lot of unknowns, it would be wise to assume the worst-case scenario. Then when we have more information, we can walk back our threat posture to a more reasonable level. Until that happens, until we get more information, I don't think we can walk things back just yet. So personally, from a risk management perspective, I myself am operating under the assumption that these are probably the effects of malign actors and that critical services and infrastructure may fail at any moment. Of course, that sounds a little bit serious to describe in that way, but I'm certainly not a cybersecurity expert, but even I am not really concerned about this being a cyber apocalypse or whatever they're saying it is these days. It is impossible to know with absolute certainty which outages are due to malign action and which ones are false flags and which ones are just the result of incompetence. A lot of this is also probably being blown out of proportion because, again, we have to engagement bait everything that we do these days, I guess. But that also doesn't mean that the concerns aren't real too. So again, it's a very hard thing to balance, and at the end of the day, it probably doesn't matter that much for most end users because the end result is the same, services going down and everything from minor inconveniences to major impacts being felt, all of which are impossible to predict. Even though many of us are quite tired with remaining on the edge of our seats, I know I'm certainly quite fatigued with it all, so I know all of you are too, it is still worthwhile to remain at least passively aware that very serious things could happen at any moment here, either at home or overseas. We could return to the war in the Middle East any day now, and if that happens, the already very tenuous financial sector might be tipped over the edge into more serious territory. Similarly, the now constant cyber attacks might also just be warnings. In the grand scheme of what's possible, hacking the FBI, grounding every aircraft in the country, and taking food stamps offline is just a light nudge, a little warning, very small potatoes compared to what is theoretically possible if a malign actor really wanted to cause problems. It's also possible that these cyber incidents are related to the war and are intended to be a nudge toward resuming that conflict. At the moment, any theory is as good as the next, and we'll just have to do the best we can to stay as ready as our fatigue and sanity allows. And speaking of staying ready on the communications front, due to the surge of cyber attacks this week, it would seem that many people are rather concerned about having resilient and robust communications, so I saw a lot more people making use of the Ghost Net this week. For those who are unaware, the Ghost Net is a shortwave radio network and communications plan which is designed to function as both an emergency network but also more regularly throughout the week as a standard information sharing service. If you are interested in learning more, uh, you can download the handbook at the links below, and I have a whole playlist on YouTube dedicated to explaining the evolution of the Ghost Net and why I thought this might be needed. This week, I have been working on making some major upgrades to this plan to make it more of a system instead of just a shared comms plan. I wanted to thank all of you who have been transmitting news reports randomly throughout the week because those transmissions have been helpful for me to develop some stuff on the software side of things, and I am almost ready to reveal a secret project I've been working on for some time now. I have been building a software solution which will bring a lot of extremely useful changes to the Ghost Net while also keeping backwards compatibility. You don't need to go print out a new guide or anything. What I'm building will layer on top of what already exists to supplement and streamline the software that we use. I hate to vague post about this so much, but I will be needing volunteers to help me with the early alpha testing of some new software. So for those of you who are interested in helping me test out some stuff, stay tuned for that. I will have a separate announcement on that later. I plan to have the first public version out by maybe next week sometime, at least to test with and hope it doesn't break too much. Otherwise, I also have a few more plugins in development that will work with ATAC as well as TACx. I am indeed in the process of updating all of my plugins to be compatible with TACx right now, which has taken quite a bit of time as there aren't enough hours in the day, but I'm working to get updates out as soon as possible. So all of that considered, I think that's all I have for today. As always, all of my work is available for free on a variety of platforms. Uh, Obsidian hosts all of my notes and source material for every report. You can also find the same stuff on my Nomad Net for those of you who use Reticulum and Mesh Chat X. Also, my ArcGIS pages host all of the mapping data that you see, and all of that can be accessed from just a simple web browser, so you don't have to download anything if you wanna look at my maps and click around the stuff that I build every day. For those who want a more tailored or offline cache of my data for data hoarding purposes, you are in luck because you can download the raw KMZs from my GitHub page, or you can try out my new Ghost Maps plugin, which is also on GitHub, which allows you to more easily download all of my map layers and keep them updated when I push out updates. So if you are confused about something that you see on a map or if you're wondering, "Hey, what's that symbol mean?" well, you can either go to the ArcGIS online maps, or you can download and, uh, get involved in the ATAC stuff so that you can get a little bit more awareness of what each point means and what it's actually there for. So thanks again, everyone. I really do appreciate the support, and I really hope to push out some helpful solutions soon, which will help us all be more prepared and capable no matter what challenges lie ahead. It's pretty crazy times out there, but I think we'll do all right. So thanks again, and I will see you next time. And as always, fight in the shade.
Bibliography
no sources referenced for this publication