Bible Code Reassured Wolfowitz of Success In Iraq?
Is It Good For The Jews?
By Bill Keller
March 8th, 2003
The New York Times
Two weeks ago, a group of senior intelligence officials in the Defense Department sat for an hour listening to a briefing by writer Michael Drosnin who claims — I am not making this up — that messages encoded in the Hebrew text of the Old Testament provide clues to the whereabouts of Osama bin Laden.
========================
Now for Drosnin’s version….
========================
SECRET PENTAGON BRIEFING
At the height of planning a war against Iraq, in the middle of a fierce debate over the war at the United Nations, just two days after the White House put the country on a “high terror alert,” I received an urgent phone call. “Can you come to Washington?” asked Dr. Linton Wells, director of the Pentagon’s nerve center. It was Sunday morning February 9, 2003. I was surprised to get a call over the weekend from a key member of America’s invisible government, not the government we read about in the newspapers and see on television every day, but the top secret permanent government we never see. Wells was the man who ran C3I — military shorthand for Command, Control, Communications, and Intelligence. “Sure,” I said. “What brings you out on a Sunday?” “The Deputy Secretary,” said Wells, referring to his boss Deputy Secretary of Defense Paul Wolfowitz. “He just called me out of an important meeting in Colorado, and asked me to arrange for you to brief the Pentagon.” “You know I don’t have any hard information, Lin,” I told Wells, who I had known for years as a reporter who covered, and at times shared secrets with the intelligence agencies. “It’s the Bible code, right?” said Wells.
Now I was really surprised. President George W. Bush was preparing to declare war against Saddam Hussein, and in the middle of the late night strategy meetings, the architect of the war, the second highest official in the Pentagon had just ordered his top deputy to arrange a briefing on a 3000 year old code in the Bible that revealed the future. “Why the sudden interest, Lin?” I asked. “I don’t know,” said Wells. “I just follow orders. But Wolfowitz did mention the Chief of the Mossad.” I had met with the Chief of the Mossad, Gen. Meir Dagan, three times, and the head of Israel’s famed intelligence agency took the warnings in the Bible code so seriously that he urged Prime Minister Ariel Sharon to meet with me. Now, apparently, the Americans wanted to know what I had told the Israelis, and what else I knew about the dangers that might lie ahead. “Who’ll be at the meeting?” I asked Wells. “Admiral Jake Jacoby, Director of the Defense Intelligence Agency, and someone from the Operations Directorate of the Joint Chiefs of Staff,” Lin said. “Of course, I’ll be there on behalf of Wolfowitz.” Wells had just named the entire top command of American military intelligence. Admiral Lowell “Jake” Jacoby ran the DIA, the biggest spy network in the world, far bigger than the CIA. The Department of Defense controlled 85% of the intelligence budget, including the National Security Agency, which listened in on the world, and the National Reconnaissance Office, that watched the world with spy satellites constantly orbiting the globe. The Joint Chiefs had authority over the Army, Navy, and Air Force, and its Operations Directorate handled the most sensitive missions. Wells himself was not only Wolfowitz’s top deputy, his go-to man, but orchestrated everything out of C3I, the heart of our entire military. It was clear that the Pentagon took the Bible code very seriously. “Can you be here next week?” asked Wells. “I’ll be there,” I said.
Two days later Osama bin Laden, still alive, still on the loose, still hidden, issued a new audio-tape broadcast over the Arabic news network Al Jazeera, warning of revenge for the looming war against Iraq. The country was already on a “high terror alert” for only the second time since the September 11, 2001 attacks. President Bush himself had signed off on the order. Now bin Laden made the threat explicit, and urgent. “Fight these despots,” urged the terrorist leader who had ordered the 9/11 attacks. “All who cooperate with the Americans against Iraq are hostile to Islam. We stress the importance of martyrdom attacks against the enemy.” CIA Director George Tenet told a Senate committee that “the continuing threat remains clear.” “Al Qaeda,” he said, “is still dedicated to striking the U.S. homeland.” In a joint appearance, Tenet and FBI Director Robert Mueller warned that terrorists were seeking chemical, biological and nuclear weapons to use against America. “The enemies we face are resourceful, merciless and fanatically committed to inflicting massive damage on our homeland,” said Mueller. Secretary of State Colin Powell also warned that “Al Qaeda, bin Laden, other terrorists, are trying to develop weapons of mass destruction.”
By the time I arrived at the Pentagon, Washington, D.C. was under tight guard, with F-16 fighter jets flying overhead, and armored vehicles mounted with Stinger anti-aircraft missiles patrolling the streets of the nation’s capital. At 9AM on Friday, February 21, 2003 I met with the top ten leaders of U.S. military intelligence in a conference room in the E ring of the Pentagon, the inner circle reserved for the Office of the Secretary of Defense. And I briefed them about a 3000 year old code in the Bible that warned we had only four years to figure out some way to survive, to prevent a nuclear World War III. “At the request of Secretary Wolfowitz, I’ve come today to brief you about a code in the Bible that appears to reveal events that happened thousands of years after the Bible was written,” I told the American intelligence officials seated around a big conference table, handing each of them a memo that described the ancient Hebrew code. “It was discovered by a famous Israeli mathematician, and confirmed by a senior code-breaker at the U.S. National Security Agency,” the memo stated. “I believe the code is real for a simple reason: it keeps coming true.” I gave the intelligence officials computer print-outs that made the point dramatically. “The events of September 11 were encoded in detail,” I said. “Twin Towers” appears with “Airplane” and “it caused to fall,” all in a text that is 3000 years old.
The intelligence chiefs were clearly impressed. They studied the ancient Hebrew characters. I told them that these same words had appeared in every Israeli newspaper headline the next day, and were encoded together in the Bible against odds of 10,000 to 1. I showed the American intelligence leaders a graphic image in the Bible code of the Columbia space shuttle disaster, the mid-air explosion that had killed seven astronauts just a few weeks earlier on February 1. Not only was “Columbia” encoded with “shuttle” and “fire will destroy,” but the encoding created an actual picture of the spaceship, and looked at from launch position the words “fire will destroy” formed the left wing. In fact, a fire starting in the left wing triggered the disaster.
Finally, I handed them copies of the letter I sent Israeli Prime Minister Rabin more than a year before he was killed warning him the Bible code predicted his assassination. The code table could not be more explicit: “Assassin will assassinate” crossed “Yitzhak Rabin,” the one time his full name was encoded in the Bible.
I clearly had their attention. This Hebrew code in the Bible, as unbelievable as it seemed, consistently came true. The top command of U.S. military intelligence was as interested as the leaders of Israeli intelligence. “You warned Rabin a year in advance?” asked Adm. Jacoby. “How did the Israelis react when he was killed?” “That’s when the Israelis began to take the Bible code very seriously,” I replied. “I met with the new Prime Minister, Shimon Peres, and also briefed the man he had just made the Chief of the Mossad.” Now I told the Pentagon officials who controlled all the hardware, all the technical resources of the world’s one remaining superpower, what I had really come to say. “The main reason I’ve come to see you today,” I said, “is that the code warns that we may face the ultimate danger — a nuclear World War, starting in the Middle East — within four years.” I told them that “World War” and “Atomic Holocaust” and “End of Days” were all encoded with the same year, 2006 — against odds of at least 100,000 to 1. “That doesn’t leave much time,” said Adm. Jacoby. “How clear is it, and if it’s predicted, what can we do?” “The famous Israeli mathematician who discovered the code said that this could not happen by chance,” I said. “It had to be intentionally encoded in the Bible. But I’m certain the danger can be prevented,” I added. “The Bible code reveals probabilities, every future, and what we do determines what actually happens.” “What does it say about Iraq?” asked Lin Wells, focusing on the immediate danger.
“Good news,” I said, handing him another code table. “It says that Saddam Hussein will fall in 2003. It’s encoded in the form of a question and answer: “Who is destroyed? Hussein.” And crossing his name, against very high odds, is the year, 2003.” “There’s more,” I told Wells, showing him a more detailed version of the same code table. “It says Saddam will flee, but it also indicates that he will die.”
“The same thing is encoded again — that Hussein will be forced to flee, but will die,” I said, again passing the computer print-out around the conference table. “So the outcome is already determined?” asked the man from the Joint Chiefs, who arrived late.
“No,” I said. “The Bible code is not a crystal ball. It reveals probabilities. Nothing is set in stone. But it does provide detailed information you can check out.” “However, I don’t think the real danger is Saddam Hussein, but Osama bin Laden,” I added. “Of all the information we’ve found in the Bible code one thing stands out as most useful — a clearly stated location where bin Laden, the headquarters of Al Qaeda, and all of their most dangerous weapons might be found.” There was a stunned silence. “That would be useful,” said Adm. Jacoby, breaking the silence. I gave the men who were running the hunt for bin Laden one code table after another that named the exact remote desert location, with the precise co-ordinates. “You won’t publish this, will you?” asked Wells. “Of course not,” I said. “The information is for you, not bin Laden. If I tell him, he won’t go there.” The name of the same terrorist base crossed both Hebrew spellings of “bin Laden” against odds of at least 10,000 to 1. One of the times the full hidden text stated “Army Headquarters in X.” “It might also be the location of unconventional weapons, perhaps the source of ultimate danger to the United States and the world,î I said. I showed them that the same obscure place in the Middle East was also encoded with “atomic weapon” and “atomic holocaust” and “smallpox.” Where “Army Headquarters in X” crossed “bin Laden, “missile” overlapped both in the code.
And I showed them that the terrorist base was encoded with three of the most likely targets, “Jerusalem,” “Tel Aviv” — and “New York.” “The Bible code clearly suggests that New York has not yet witnessed the worst danger,” I said. “September 11 was the beginning, not the end. And it’s all in some way tied to Al Qaeda and this same hideout.” “I don’t want to sound Apocalyptic,” I told the military leaders, “but the full scale of the danger is captured only by the words of Biblical prophecy.” “In the End of Days” appears in the original words of the Bible, crossed by “terrorism” and the name of this base,” I said. “In fact, the code states that “terrorism” will be “coordinated from hiding place X,” “in the End of Days.” I had been worried about sounding too religious, when in fact I was not religious at all, but no one in the room raised a question. I realized it was likely many, even most of the intelligence leaders were religious, and like the President himself, believed in the “End of Days.” Certainly, they all believed in the danger. At the highest levels of our government there was unanimous agreement that new terrorist attacks, on a yet greater scale, were almost inevitable. Everyone from the President on down had said it publicly. We were in a third world war, unlike any war we had ever fought before, because the enemy was hidden. And I guessed that one of the reasons this meeting had been called, that I had been asked to brief the Pentagon about the Bible code, was that on some deep level everyone knew we needed a miracle. “There’s one problem,” I said as the hour came to an end. “I can tell you where to look, but not when. I’ve never seen anything as clearly encoded as the location of this terrorist base, of bin Laden, but the code does not state a year. I can only suggest that you look now, and again, and again - because if you succeed you will stop terrorism at its source.”
The most senior official there, the director of the Defense Intelligence Agency, Admiral Jacoby, spoke up. He was not addressing me, but all the other military men in the room. “If you looked at Normandy one day it was just a beach,” said Jacoby. “If you looked the next day, it was D-Day.” He had given our military intelligence command its marching orders — target our satellites on the location the Bible code named as bin Laden’s hideout, and don’t stop looking until you find him. My Pentagon briefing had lasted a full hour. Not one of the important people there had left even for a moment to take a phone call. The only people in the world with the military resources to make use of the information in the code had clearly taken it totally seriously. As I walked down the steps of the Pentagon, the enormity of the moment, of who I’d just met with, of what I’d just told them, of what was happening in the world, made me think of the words I said out loud when I saw with my own eyes the attack on New York September 11 — “Oh my God, it’s real.” My last doubts had been wiped out that day. I stood on my roof, watched the World Trade Towers fall, and then found the entire horror encoded in a 3000 year old text. What I had seen happen only minutes earlier was now on my computer screen in ancient Hebrew characters. On the train back to New York from my Pentagon briefing it all hit me. I had been at the center of the inner sanctum of the invisible government. I had met with its leaders. And they had believed me.
I had told the most important people in American military intelligence that we faced a danger so great it was only captured by the words of Biblical prophecy — “Armageddon,” the “End of Days,” the “Apocalypse” — and they had taken this Hebrew code in a 3000 year old text so seriously that the full resources of the Pentagon would now be committed to preventing the horror. “The data has been input,” said Lin Wells when he called from C3I a few days later. “The coordinates are in our satellite system. Your meeting went very well. All the intelligence people are taking this very seriously. I briefed Wolfowitz. We’re already looking for bin Laden.” But I knew that the war in Iraq would soon divert the U.S. from its search for the fugitive terrorist leader, and I feared that although we might forget about him, he would not forget about us. I flew to Israel and met with its top intelligence analyst, General Yossi Kuperwasser, at Israeli military headquarters the Kirya. I had met with Kuperwasser before, and like most officials at the highest level of Israeli intelligence he listened to the warnings in the Bible code because they kept coming true. The code also agreed with Israel’s own best estimate of when it might face an “atomic holocaust” — 2006. I showed him a new code table. “In Jerusalem” was encoded with “mega-terror” and “war,” crossed by “bin Laden.” “The odds against it happening by chance are three million to one,” I told Kuperwasser. “Bin Laden is going to strike Israel if you don’t find him first.” I had already given the Israelis the same information I had given the Pentagon, the name of bin Laden’s hideout encoded in the Bible. “We already looked,” said Gen. Kuperwasser. “We’ll look again. We’ll keep looking.” I knew they would. The Israelis had a very clear sense that their survival was at stake. They did not have our technical resources. Just a very strong will to survive.
But the United States, according to all reports, was as vulnerable to a terrorist attack today, as it had been on September 11. “A year after 9/11, America remains dangerously unprepared to prevent and respond to a catastrophic attack on U.S. soil,” said a Council on Foreign Relations report issued in October 2002. “In all likelihood, the next attack will result in even greater casualties.” And on July 24, 2003 a bi-partisan Congressional report made a scathing indictment of the intelligence community for failing to prevent 9/11, and warned that we were still not prepared to prevent another terrorist attack. On the same day I sent a new letter to Deputy Secretary of Defense Wolfowitz. It stated: “I believe the next major terrorist attack is not far off, and that this time we may lose an entire city, not just two tall buildings. There is a warning of a new attack on New York, perhaps as early as 2004.” The attack on September 11, 2001, had been encoded in the Bible for 3000 years. But we had failed to find the warning until it was too late. On the day of the attack, right after the towers fell, the Israeli scientist who discovered the code, Dr. Eliyahu Rips, had found the Hebrew date equivalent to September 11 crossed by “Twin Towers.” In the same place, the original words of the Bible said, “And there fell of the people that day about three thousand men.” “All of the first newspaper accounts, all the television reports, said that the number dead was six thousand,” said Rips. “It wasn’t until months later that we found out it was really three thousand. But the Bible code stated the true death toll on the day of the attack.”
Now, as the countdown from 9/11 to Armageddon continued, I again searched the code. There were two years encoded with “New York,” 2001 and 2004. And crossing 2004 were ominous words: “from the fire of a missile.”
The danger might be right upon us. I asked Dr. Rips to re-calculate the odds against all of it — the city, the two years, the danger — appearing together in the Bible. “It is at least 10,000 to 1,” he told me. And now we saw that exactly the same warning, “from the fire of a missile,” also appeared against very high odds with five related dangers in the Bible code. “War of terrorism” was encoded with “from the fire of a missile,” as was “chemical attack” and “atomic weapon.” “Terror, 5764,” the Hebrew year equivalent to 2004, was also encoded with “from the fire of a missile,” apparently confirming next year as a strong probability. Finally, “from the fire of a missile” was crossed by “the war started.” It suggested that a terrorist missile attack might trigger an all-out war. Dr. Rips calculated the odds again and said that taken all together it appeared that the probability was many millions to one. The Bible code clearly suggested a missile as the weapon, terrorists as the enemy, and New York as the target — perhaps as early as 2004. But every year in the near future was encoded in the Bible with great danger, in New York and on a global scale, until it peaked in 2006.
At the end of July 2003, just before President Bush left the White House for an August vacation at his ranch in Crawford, I sent him a new letter through his friends in Texas. It warned: “The Bible code states the final danger in modern terms — “Atomic Holocaust” and “World War” are both encoded in the Bible. And both are encoded with the same year — 2006.” For years I had been warning world leaders that an ancient prophecy was about to come true, that the Apocalypse long foretold by all the West’s three major religions was also encoded in the Bible. On September 11 I had seen it begin to unfold just down the block from my home in New York. Now it seemed that the warning I just sent President Bush might come true almost immediately: “September 11 was not the end of the danger, but the beginning.”
Copyright 2004 Michael Drosnin
(In accordance with Title 17 U.S.C. Section 107, this material is distributed without profit to those who have expressed a prior interest in receiving the included information for research and educational purposes.)
