A key point in the discourse over Indian H-1Bs and offshoring is that they not only represent a danger to American jobs and well-being, but they pose a national security risk. I can now report that Iron Mountain, Boeing, and other companies who handle sensitive government and military data have been heavily infiltrated by Indians, either via offshoring or the mass hiring of H-1Bs and other visa holders. This would be a scandal if it involved foreigners from any nation, but India’s status as a BRICS member and its close alignment with enemy states like Russia and China means that this represents an exceptionally grave risk to American national interests. The fact that Indians have already been implicated in hacking and data breaches on behalf of China makes this even more alarming.
Iron Mountain is an information management company that manages sensitive records and other data for numerous corporations as well as the federal government. Earlier this year, Iron Mountain was in the news after Elon Musk, in his capacity as head of DOGE, criticized the Office of Personnel Management for leasing a cavern from the company to store and process retirement paperwork for government employees.
According to multiple insiders at Iron Mountain, it’s “impossible to get a job” at Iron Mountain “if you are white,” and the company hires Indians almost exclusively for senior roles and have access to large amounts of information from the government and corporations. Additionally, I’ve received reports that the company is purging white American employees in favor of Indians. The insider states that Iron Mountain is in the process of “cost-cutting” and is outsourcing as much of its work as it can to notorious Indian bodyshop Tata Consultancy Services (TCS) (I’ve written about TCS here). This has led to many competent white employees being fired “and a drastic reduction in quality of work. Lots of processes have slowed or come to a complete halt.”
Anyone inside Iron Mountain voicing concern about this is ignored. Iron Mountain’s “white employees know its just a matter of time before things collapse in on itself from the structural black hole that upper management is creating for itself.” The only non-Indians who are still working at Iron Mountain “are senior/very technical/experienced people or people in work who cannot be replaced by people outside the country (e.g. security cleared).” The insider states that these are the only people still “holding the company together.”
It’s likely that Iron Mountain’s increasing reliance on Indians is the source of many of its recent problems, such as its admission last year that a fifth of the hard disks it is storing for customers are inaccessible, the data on them lost. The presence of large numbers of Indian nationals at a company tasked with handling sensitive corporate and government data represents a massive national security concern.
Have you been wondering why Boeing planes seem to be crashing more often? Boeing being taken over by Indians on visas might have something to do with it. Boeing is also allowing Indians to access sensitive defense data in violation of federal law.
According to an insider, Boeing’s HR is almost entirely Indians and if you call the HR help line, “100 percent it will be picked up by an Indian who can barely speak English.” Indians are also responsible for passport and identity verification at Boeing. The insider says these Indians are either offshored or hired through bodyshops.
The insider describes Boeing’s software engineering as a “mess,” noting that Boeing has access to sensitive data related to defense manufacturing. While federal law prohibits foreigners from accessing or working with this data, Boeing has been circumventing this law by having American engineers “mask” or “scramble” the data so offshore/bodyshop Indians can work on it. Indian hiring managers at Boeing, per usual, always defend and promote other Indians: “They always find a way to bring the ‘Indian team’ onto any project, even if it is a highly sensitive defense project.”
Another insider reports that when it came time for Boeing to do his background, it was outsourced to HireRight, and when he called support a couple of times for clarification, he was greeted with Indians who could barely speak English, as well as an ancient website. His I-9 verification was offshored to TCS and email/video contact was with another Indian. The onboarding process is also done by Indians.
Iron Mountain and Boeing are far from the only examples of federal contractors that have been taken over by Indians. Qualcomm, a federal contractor and major manufacturer of semiconductors, is in the process of replacing its American workforce with Indians.
Qualcomm recently initiated a hiring freeze and has laid off American employees. Unstated is that the CFO, Akash Palkhiwala, has no intention of hiring Americans and will simply hire in India instead. According to an insider, in one team within QCT, every single general manager is now Indian. The CFO has set a goal to have 30 percent of the workforce in the U.S. and 70 percent in India. Additionally, at Qualcomm’s recent 40-year-anniversary celebration in San Diego, roughly three-quarters of the attendees were Indian.
Qualcomm’s Bangalore and Hyderabad sites are now bigger than its San Diego HQ in terms of employee count. Increasingly, the top positions at Qualcomm are being taken over by Indians, as non-Indians are fired or otherwise pushed out. The general manager of mobile connectivity recently departed the company and was replaced with an Indian. This has happened enough times since Palkhiwala took over that it’s likely intentional behavior on his part. The whistleblower believes he is the one actually running Qualcomm and the CEO is just a token.
Anonymous posts at TheLayoff.com confirm much of what the whistleblower is saying. Quote:
The truth is that Q[ualcomm] passes o[ver] we qualified Americans every day. Or pushes them out. Hiring managers are former H1Bs that hire from their caste and work new, less qualified H1Bs to the bone. And eventually toss them out.
But new American grads and old timers are done in this industry.
Another insider at Qualcomm reveals the extent to which the company has been taken over by Indians. According to the insider, when Qualcomm began growing in the 90s, it was “overwhelmingly, predominantly white,” but when Indians started being hired and rose through the ranks—specifically when they started being placed in charge of hiring—Qualcomm began hiring Indians on H-1B visas exclusively. They also began offshoring work to India itself, with the end result that there are almost no white people left at Qualcomm’s San Diego headquarters. One now-retired Qualcomm employee said that for the longest time, he was the only white person on his floor.
When Qualcomm’s hiring was still controlled by whites, they hired on merit and discovered that some of the best engineers in America were whites from Midwestern states like Iowa or Nebraska. None of them can get a job with Qualcomm now due to the Indian hiring managers; the insider reports that “[t]here’s entire floors at Qualcomm where people only speak Hindi or Telugu.”
Additionally, Qualcomm’s position as a major manufacturer of electronic logging devices (ELDs) presents another security risk. Every semi-truck in the U.S. is required to have an electronic logging device (ELD) in their cab, and Qualcomm’s dominance of the industry is such that truckers often refer to ELDs as “Qualcomms.” While there are other ELD manufacturers now, virtually all ELDs are compromised to some degree. In particular, companies like to buy ELDs from shady fly-by-night operators because they can then edit the devices to force their drivers to be on the road longer than is legally allowed. It’s likely a great deal of the accidents caused by Indian H-1B truck drivers are due to ELD tampering forcing them to drive past the point where it is safe.
To make matters worse, ELDs that have been tampered with in this fashion can be hijacked by bad actors. Hackers and the like can gain access to a driver’s phone and even make spoof phone calls using an ELD. A lot of cargo thefts in the past five years are the direct result of hacked ELDs. The FBI has issued warnings about hacked ELDs to no avail.
One comforting details is that another insider at Qualcomm told me that there is nothing shady going on with the ELD (fleet) side of Qualcomm’s operations, as their data centers are still run by the same team that has been in charge for a decade. This team is the only group that has access to raw data and there are no backdoors for anyone else to access it. However, this same insider reports that over the last six years, the number of Indians on payroll has increased to the point where they are now half of Qualcomm’s workforce. This is in the U.S., but Qualcomm in Canada is also being taken over by Indians. The Indians haven’t yet infiltrated Qualcomm in Mexico (due to how seriously the Mexicans take freight safety), but Qualcomm’s European operations are steadily being taken over by Indians as well. Report:
If you really want to dig into some things. Start with Vista Equity. They bought Omnitracs after Qualcomm separated the trucking side. Vista has been in many tax evasion cases and seem to be a bit shady. They had Omnitracs for sale for years before they “sold it” to Vista’s Solera company.
Another prominent federal contractor, Project Kuiper, has been taken over by Indians and Chinese on visas. Project Kuiper was established in 2019 to deploy satellites that can provide Internet access to remote regions of the world. It also supports the U.S. military’s Hybrid Space Architecture project, which aims to provide reliable Internet connectivity for the military, as well as the militaries of America’s allies.
Project Kuiper’s vice president is an Indian named Anand Victor:
An insider reports that there are numerous examples of non-Indians being rejected for jobs with Project Kuiper, as well as the usual stories of Americans being laid off and replaced with Indians or being passed over for promotion in favor of less-experienced Indian colleagues. Victor is extremely unpopular with Project Kuiper’s American staffers, one of whom calls him a “dick”:
Below is a number of screenshots of Project Kuiper’s teams:
As you can see, the teams are primarily comprised of Indians and Chinese. Given Project Kuiper’s close association with the military, this is a national security risk.
The insider informs me that there “may also be suspicious contracting/sub-contracting going on” and adds that people have been complaining about Indian discrimination against Americans via Amazon’s internal ethics system, but Amazon has yet to take any action.
Allowing Indians to work at defense and other federal contractors is mystifying. India is not only not an ally of the U.S., it is a member of BRICS, an explicitly anti-Western trade bloc and military alliance whose other key members—Brazil, Russia, China, and South Africa—are hostile to the U.S. India has historically been hostile to the U.S.; during the Cold War, Soviet intelligence penetration in India was some of the highest in the third world, to the point that famed defector Yuri Bezmenov, stationed in India, had to concoct an absurd escape plot to avoid Indian police ratting him out. We don’t need to speculate on the national security risks of allowing citizens of a hostile state access to sensitive defense data, because Indians have already been caught in a major national security-related data breach.
In a video provided to me, former Anthem/Elevance Health employee Nathan Sass details the 2015 Anthem data breach—in which the Chinese government stole nearly 80 million records from the company—the role Indian employees played in it, and its similarity to the recent Grok code theft. In the video, he mentions that he was laid off from his job several months prior while “H-1B visa holders were retained after I got laid off.” I’ve transcribed the most relevant parts below.
The Anthem data breach involved the theft of 78.8 million records from the company, encompassing personally identifiable information (PII) such as Social Security numbers, names, and addresses as well as private health information (PHI). Sass notes that no financial information was stolen, which he regards as suspicious. Contrary to what was reported in the media at the time, the Anthem data theft was not done via spear phishing, but via a machine-level administrative account in the “Edward” data warehouse. These accounts cannot be created externally without internal approval and Sass himself did not possess this level of access despite his lengthy tenure and extensive responsibilities at Anthem. While the FBI indictment states that the Anthem data breach began in 2014, Sass’ information led him to believe it had been going on far longer than that.
Sass argues that the breach was most likely committed by offshore IT contractors in India who the Chinese bribed with Bitcoin. Afterwards, Anthem ended their relationship with several Indian contractors, adding to Sass’ suspicions. The motivation for the hack was due to the fact that Anthem carried coverage for multiple defense contractors at the time, including Lockheed Martin and Northrop Grumman, and “the names and claim history” of associates of these companies were compromised in the hack: “Right around that time, it is known that China was rapidly advancing in their fifth generation fighter, the J-20, which bears a striking resemblance in many ways to the F-22 Raptor, which was concurrently being built by Lockheed Martin.”
Sass believes the FBI deliberately buried the case not simply out of embarrassment that China ripped off the F-22, “but also because major financial interests have quite a stake in the continued use of offshore and H-1B visa holders in the IT field to suppress wages and increase profits.” He compares the case to the recent case of Xuechen Li, a Chinese H-1B holder who stole Grok’s code base, joined OpenAI, and is now being sued by Elon Musk. Sass argues that Xuechen Li also likely gave Grok’s code base to the Chinese government.
Sass reiterates in the video that any data you provide to a corporation is unsafe if that corporation offshores any operations to India. Indians have no concept of morality as Americans define it; they will do anything—including lying, cheating, and stealing—to get ahead. For corporations, Sass argues that India is the primary vector China uses for IP theft. It’s much easier to convince an Indian to commit these crimes than an American because Indians simply don’t care.
Sass closes by demanding the FBI declassify the Anthem data breach investigation. “There is a John Doe who’s never been named who was indicted along with a named Chinese person that was directing the hack according to the indictment.” The FBI is hiding what happened from Americans and we must know the truth.
Given the evidence that Indians have been responsible for data breaches at numerous other corporations, such as Coinbase, allowing them to work for defense and federal contractors such as Qualcomm, Iron Mountain, and Boeing can only be described as suicidal. Indians are no doubt trying to steal as much data as they can from these corporations, funneling it to China or simply selling it to the highest bidder. They have no ethics, no loyalty to America, and no reservations about selling out their employers to make a quick buck.
The federal government must act in prosecuting these companies and ending their contracts unless they purge all Indians and other foreign nationals from their workforces. The safety of Americans is at risk.
If you are a whistleblower/have insider information from Boeing, Iron Mountain, Qualcomm, or any other corporation engaged in similar abuses, feel free to reach out to me via Substack DMs, X/Twitter DMs, or email at mattforney [at] protonmail [dot] com. All communications are confidential and your anonymity will be protected.
If you enjoyed this article, please consider subscribing by clicking here. Most articles on this blog are free, but your support gives you access to paywalled articles and enables me to do this work. You can also make a one-time donation here (note: this does not give you access to paywalled articles, unfortunately). Follow me on X/Twitter, where I post stories more frequently, here.
