Sunday, March 8, 2026

5 Surprising Secrets of Fort McClellan’s Pelham Range

 Mustard Gas and Mock Nukes: 5 Surprising Secrets of Fort McClellan’s Pelham Range

For decades, the dense pine forests of Pelham Range served as the epicenter of the U.S. Army Chemical School. It was a place where Cold War readiness was forged through exposure to the world’s most feared substances. But as the 1995 Base Realignment and Closure (BRAC) process began to dismantle Fort McClellan, a darker environmental legacy emerged from the Alabama red clay.The "Toxic Gas Area" wasn't just a name—it was a literal description of a landscape saturated with chemical agents, radioactive isotopes, and unexploded ordnance. As these parcels are scrutinized for transfer to the National Guard or the public, investigative reports have revealed the high-stakes audacity of a training ground that once simulated the end of the world.

1. The "Atomic Pond" and Simulated Nuclear Fallout

During the 1950s, the Chemical Corps didn't just teach soldiers how to survive a nuclear strike; they built a mock wasteland to prove it. At Station No. 5—officially known as Range L—instructors created a man-made crater known as "Lima Pond."To simulate "residue from an atomic bomb," live radioactive sources were placed within the crater. Trainees were forced to navigate this simulated nuclear "ground zero," using Geiger counters to map the invisible lethality of the pond. While the radioactive materials have since been removed, the existence of a mock-atomic blast site in rural Alabama remains a chilling reminder of the era's training intensity.

2. The Gauntlet: A Seven-Station Chemical Obstacle Course

From 1955 to 1963, the Army operated a "chemical obstacle course" designed to overwhelm the senses. This was no mere exercise in physical endurance; it was a seven-station gauntlet where soldiers were exposed to a rotating menu of toxic simulants and riot control agents.The course utilized a sophisticated array of chemicals across specific stations:

  • Stations 1 & 2:  Chloroacetophenone (CN) and adamsite (DM) grenades.
  • Stations 3 & 4:  Phosgene (CG) and chloropicrin (PS), coupled with M117 booby-trap simulators.
  • Station 7:  A volatile cocktail of incendiaries and explosives.The training was so thorough that it concluded at a truck-mounted personnel decontamination station where soldiers performed rigorous face and hand washing to scrub away the day’s exposure. As noted in the 2004 Site Investigation Report:"Station No. 7 included white phosphorous, M-15 smoke grenades, HC (mixture of hexachloroethane, aluminum powder, and zinc oxide) smoke grenades, blocks of nitrostarch, M2 flame throwers, electric blasting caps, M5 smoke pots, shell simulators, and pentaerythritol tetranitrate (PETN) detonating cord."

3. Real Mustard vs. "Molasses Mustard"

The stakes reached their peak at Station No. 6 and the surrounding Decontamination Training Area. Here, the Army utilized sulfur mustard, a potent blistering agent. Trainees worked with two forms: "distilled mustard (HD)" and the syrupy, highly persistent "molasses residuum mustard (MR)."Just south of the main course, instructors conducted exercises that would be unthinkable today. They contaminated two World War II-era motorized tanks with actual chemical agent mustard (H). Soldiers then attempted to decontaminate the heavy armor using "decontamination agent noncorrosive (DANC)" or a "supertropical bleach (STB)" slurry.Sulfur mustard is notoriously difficult to eradicate. According to the Agency for Toxic Substances and Disease Registry (ATSDR), this substance can persist in the environment for years, particularly if buried in soil. For decades, the excess agent and caustic decontaminants were disposed of in burial pits near the training sites, creating long-term toxicological "hot spots" that remain a primary focus for modern remediation teams.

4. The Great Regulatory Standoff: Army vs. EPA

In 1998, as the Army prepared to shutter the post, a bureaucratic war erupted. The Army’s Environmental Baseline Survey (EBS) made the bold claim that the Pelham ranges contained "no hazardous substances" or petroleum products.The response from the EPA and the Alabama Department of Environmental Management (ADEM) was swift and scathing. Regulators pointed out the inherent irony: how could a "Toxic Gas Area" be labeled free of hazardous substances? ADEM specifically cited "known releases" of lead at pistol ranges and explosives like TNT and RDX in the soil and sediment from years of artillery fire.Because of this friction, the regulators insisted on classifying the ranges as "Category 7" parcels—the highest risk designation available. This classification effectively blocked any rapid land transfer, forcing the Army to acknowledge that decades of chemical warfare drills could not be wiped from the books with a simple survey.

5. The Hidden Map of Contamination

Decades after the last smoke grenade was pulled, the land still holds the physical remnants of its "toxic" history. A 2004 Site Investigation of Parcels 211 and 207 uncovered a graveyard of military hardware. Near the old Station No. 7, teams discovered a fragment of an M2 flame-thrower, while other areas yielded four 5- by 3-foot spray tanks labeled "Chemical Warfare Service USA, No. M33A1."The most concerning discovery was an unlabelled 55-gallon drum, found turned on its side and approximately half-full of an unknown liquid. While the drum's contents were eventually handled, the chemical signatures in the surrounding environment were more persistent.The 2004 report confirmed that  metals  remain a primary concern in the soil, while the groundwater is contaminated with both  metals and five distinct chlorinated volatile organic compounds (VOCs)  at levels exceeding health screening values. The "hidden map" of Pelham Range is no longer just a training tool; it is a technical blueprint for a multi-generational cleanup effort.

Conclusion: A Lingering Legacy

Pelham Range stands as a monument to a time when national security outweighed environmental caution. The radioactive craters and mustard-slicked tanks were once the "gold standard" for ensuring American soldiers could survive the unthinkable.But as the forest grows over the old obstacle course, the "Ghost of Training Past" remains. We are now left with a difficult reckoning: How do we reconcile the vital training needs of the Cold War with our modern responsibility to the Alabama soil? The transition of the Toxic Gas Area proves that while the soldiers have moved on, the chemistry of the past is far harder to discharge.


Monday, January 16, 2012

SGS2 IMEI Issues Reported

[GUIDE] Recover your IMEI in 9 steps.

If you did not make any backup of your EFS folder, and your IMEI is messed up, this could be your solution to recover your lost IMEI. NOTE THAT AT LEAST YOU MUST HAVE THE SHIPPED ORIGINAL EFS FOLDER ON YOUR PHONE ( even if you didn't make a backup of it yet and even it's messed up ) FOR THIS METHOD TO WORK

My history with my IMEI:

I flashed my phone with some ROMs, and I didn't backup my EFS folder before, then My SGS2 IMEI was changed to 004999010640000, and we know this is the fake IMEI that is assigned to the phone if the nv_data.bin file is messed up.
so I researched. searched all the forums and didn't find anything that could cure my phone's IMEI and set it to the original IMEI number. so I experimented and after some hours, I fixed my IMEI.
one thing that led me to the conclusion that " .nv_data " file is the thing that I need to fix the IMEI is that they share a very look alike name, and they have the same 2MB size.

PS: I restored my phone's firmware to it's original PDA, Phone and CSC, rooted it with CF-Root, and then done this procedures below
here is what I have done:

you must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.


It is interesting to know that the IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:

1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]

2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.

3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.

4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".

5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.

6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder

7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"

8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:

adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin

9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.


and DO IT ON YOUR OWN RISK.
and PLEASE MAKE A COPY OF THE ORIGINAL EFS FOLDER BEFORE DELETING IT. IT HAS IMPORTANT FILES IN IT.
and sorry for bad English.

Wednesday, February 9, 2011

Army Was Warned Not to Deploy Bradley Manning to Iraq

Army Was Warned Not to Deploy Bradley Manning to Iraq: "


Army commanders were warned against sending to Iraq an Army private who is suspected of leaking hundreds of thousands of sensitive documents to the secret-spilling site WikiLeaks.


Pfc. Bradley Manning’s supervisor at Ft. Drum in New York had told his superiors that Manning had discipline problems and had thrown chairs at colleagues and shouted at higher-ranking soldiers, according to a report by McClatchy News service.


But Manning was deployed to Iraq anyway because the Army needed his skills and was short-staffed with intelligence analysts, according to anonymous military officials who spoke with McClatchy. Manning’s superiors believed his discipline problems could be addressed in Iraq, but then they failed to properly monitor him once he got there.


The information was uncovered by a six-member taskforce that was charged with investigating how Manning was trained and whether his supervisors had made mistakes. Their report is due to be delivered to Army Secretary John McHugh by Feb. 1.


The taskforce found that although the military had followed procedures in giving Manning his security clearance, they neglected to re-assess this decision to determine whether he should have retained his clearance once he exhibited disciplinary problems.


Three officers in Manning’s chain of command could face disciplinary action over their handling of the soldier, according to McClatchy.


Manning was deployed to Forward Operating Base Hammer in Iraq in late October 2009. There, he served as an intelligence analyst with a rank of Specialist and with a Top Secret/SCI clearance. He had access to classified networks, including SIPRnet, the Army’s secret-level wide area network linked to WikiLeaks’ most high-profile releases. He allegedly began leaking within months of being deployed.


He was arrested in Iraq in May 2010, after allegedly confessing to a former hacker in online chats that he had illegally downloaded thousands of classified and sensitive documents from classified networks and passed them to WikiLeaks. He also revealed in the chats that he had similar discipline problems in Iraq, where he had punched a colleague in the face. The action resulted in his demotion from Specialist to Private First Class shortly before his arrest.


In the chats, Manning told Lamo that he first contacted WikiLeaks’ founder Julian Assange in late November 2009, after Wikileaks posted 500,000 pager messages covering a 24-hour period surrounding the September 11, 2001 terror attacks.


Manning said he had already been sifting through the classified networks for months when he discovered a classified Iraq video in late 2009. The video showed a 2007 Army helicopter attack on a group of men.


In January 2010, while on leave in the United States, Manning visited a close friend in Boston and confessed he’d gotten his hands on unspecified sensitive information, and was weighing leaking it. He allegedly then passed the video to Wikileaks in February, which published it online in April last year.


In early May, Manning was demoted after punching a colleague during an argument. “Something I never do …!?” he told Lamo.


“It was a minor incident, but it brought attention to me,” he said. At this point, his life, which was already in turmoil, began to unravel as his career began to implode.


“I had about three breakdowns, successively worse, each one revealing more and more of my uncertainty and emotional insecurity,” he told Lamo.


Last July, Threat Level reported that Manning’s behavior had raised red flags as early as 2008 when he was still in training and before he was stationed at Ft. Drum. He was admonished then for uploading YouTube videos in which he discussing classified facilities.


Manning had enlisted in October 2007 and was only three months into his 16 weeks of training as an intelligence analyst when about 25 of his fellow recruits reported him for the videos. At the time, he had completed basic training and was receiving advanced individual training at the Army’s Intelligence Center of Excellence at Fort Huachuca, Arizona.


The videos were messages that Manning shot for his family from his room at the barracks. Manning would talk about how his day was going and although he did not disclose classified information in the videos, he talked about the base’s SCIFs, secure rooms where classified information is processed.


“It was brought up to his command, and his command took action on that,” an official told Threat Level last July. “A lot of his actions back then, you couldn’t tell it would come to what it’s come to now, but it was a red flag.”


Manning was ordered to remove the videos but he did not lose his then-provisional Top Secret security clearance.

"

Internet ‘Kill Switch’ Legislation Back in Play

Internet ‘Kill Switch’ Legislation Back in Play: "

Legislation granting the president internet-killing powers is to be re-introduced soon to a Senate committee, the proposal’s chief sponsor told Wired.com on Friday.


The resurgence of the so-called “kill switch” legislation came the same day Egyptians faced an internet blackout designed to counter massive demonstrations in that country.


The bill, which has bipartisan support, is being floated by Sen. Susan Collins, the Republican ranking member on the Homeland Security and Governmental Affairs Committee. The proposed legislation, which Collins said would not give the president the same power Egypt’s Hosni Mubarak is exercising to quell dissent, sailed through the Homeland Security Committee in December but expired with the new Congress weeks later.


The bill is designed to protect against “significant” cyber threats before they cause damage, Collins said.


“My legislation would provide a mechanism for the government to work with the private sector in the event of a true cyber emergency,” Collins said in an e-mail Friday. “It would give our nation the best tools available to swiftly respond to a significant threat.”


The timing of when the legislation would be re-introduced was not immediately clear, as kinks to it are being worked out.



An aide to the Homeland Security committee described the bill as one that does not mandate the shuttering of the entire internet. Instead, it would authorize the president to demand turning off access to so-called “critical infrastructure” where necessary.


An example, the aide said, would require infrastructure connected to “the system that controls the floodgates to the Hoover dam” to cut its connection to the net if the government detected an imminent cyber attack.


What’s unclear, however, is how the government would have any idea when a cyber attack was imminent or why the operator wouldn’t shutter itself if it detected a looming attack.


About two dozen groups, including the American Civil Liberties Union, the American Library Association, Electronic Frontier Foundation and Center for Democracy & Technology, were skeptical enough to file an open letter opposing the idea. They are concerned that the measure, if it became law, might be used to censor the internet.


“It is imperative that cyber-security legislation not erode our rights,” (.pdf) the groups wrote last year to Congress.


A congressional white paper (.pdf) on the measure said the proposal prohibits the government from targeting websites for censorship “based solely on activities protected by the First Amendment of the United States Constitution.”


Oddly, that’s exactly the same language in the Patriot Act used to test whether the government can wiretap or investigate a person based on their political beliefs or statements.


Photo: LeSimonPix/Flickr


See Also:


"

Anonymous Hacks Security Firm Investigating It; Releases E-mail

Anonymous Hacks Security Firm Investigating It; Releases E-mail: "


A U.S. security firm that claimed to have uncovered the real identity of Anonymous members responsible for a recent spate of web site attacks became a victim of Anonymous itself, when members of the online vigilante group breached the company’s network and stole more than 60,000 internal e-mails.


The group posted the e-mail spool Sunday on the Pirate Bay torrent site for anyone to download and sift through.


HBGary Federal, which does classified work for the U.S. federal government among other security work, claimed it had been working with the FBI to unmask hackers behind recent denial-of-service attacks against PayPal, Visa, MasterCard and Amazon. Members of Anonymous — a loosely structured group of internet troublemakers — had organized the mass attacks after the companies suspended accounts used by WikiLeaks to receive donations and host documents. More recently, members of the group directed denial-of-service attacks against government web sites in Tunisia and Egypt.


Last month, the FBI announced it had executed more than 40 search warrants against people suspected of participating in the WikiLeaks-related attacks. British police also arrested five men in relation to the attacks.


The hack against HBGary Federal occurred after the Financial Times published a story on Saturday quoting Aaron Barr, CEO of the company. Barr said his company’s researchers had uncovered clues to the real identities of top members of Anonymous by monitoring chat rooms and Facebook groups they frequented. Barr identified a co-founder of the group, who goes by the name Q, and said he planned to give some of the information to the FBI. He also planned to present his findings at the RSA Security Conference in San Francisco next week.


On Sunday, Anonymous ridiculed the company’s research skills and the accuracy of its data in a press release posted at Daily Kos, mocking the company’s “infiltration of our entirely secret IRC server anonops.ru and in particular our ultra-classified channels #opegypt, #optunisia, and, of course, #reporters, which itself is the most secret of all.”


In addition to the sudden disappearance of Anonymous leader Q, Anonymous co-founder Justin Bieber also disappeared just before his top-secret mission to Eritrea to offer physical succour to the rebels, suggesting that Mubarak is in our base, eating our Cheetos, likely with military support authorized by Hill Dawg.


The group then hacked into the HBGary Federal web site and e-mail servers, and replaced the web site content with a lengthy message taunting the security firm for failing to protect its own network and for trying to gain attention by marketing its research on Anonymous.


“Your recent claims of ‘infiltrating’ Anonymous amuse us, and so do your attempts at using Anonymous as a means to garner press attention for yourself. How’s this for attention?,” the message reads. “You’ve tried to bite at the Anonymous hand, and now the Anonymous hand is bitch-slapping you in the face.”


The hackers then posted a file purporting to contain the research that Barr had collected on Anonymous members as well as more than 50,000 e-mails in Barr’s account. The group claimed to have financial details for the company and threatened to erase content on the company servers.


The group also hijacked Barr’s Twitter account, sending out tweets as Barr, including a home address and Social Security number purporting to belong to him.


In addition to the HBGary site, the hackers gained root access to Rootkit.com, an online forum dedicated to analyzing and developing stealthy “rootkit” malware technology. The forum was founded by Greg Hoglund, CEO of HBGary, a separate security firm that owns about 15 percent of HBGary Federal. They seized Hoglund’s e-mail account and then posed as him in order to manipulate a Rootkit.com administrator named Jussi Jaakonaho into giving them root access to Rootkit.



Hoglund, Barr and Hoglund’s wife Penny, president of HBGary, tried to negotiate with the hackers via phone and chats to get the company’s data taken down, stating that Hoglund’s e-mails shouldn’t be exposed because he has little to do with HBGary Federal and that disclosure of some of the data would cost his company millions of dollars. The group ultimately agreed to remove links to the published e-mails for this reason, according to an online post from an Anonymous member.


Hoglund declined to comment on the hack.


See also:


"