ie8 fix

Between the Lines

Larry Dignan, Andrew Nusca and Rachel King

Fannie Mae IT contractor indicted for planting malware; Mortgage giant didn't revoke server privileges

By | January 29, 2009, 6:46am PST

A former Fannie Mae IT contractor has been indicted for planting a virus that would have nuked the mortgage agency’s computers, caused millions of dollars in damages and even shut down operations. How’d this happen? The contractor was terminated, but his server privileges were not.

Rajendrasinh Makwana was indicted on Tuesday in the U.S. District Court for Maryland (press reportscomplaint and indictment PDFs). From early 2006 to Oct. 24, Makwana was a contractor for Fannie Mae. According to the indictment, Makwana allegedly targeted Fannie Mae’s network after he was terminated. The goal was to “cause damage to Fannie Mae’s computer network by entering malicious code that was intended to execute on January 31, 2009.” And given Fannie Mae–along with Freddie Mac–was nationalized in an effort to stabilize the mortgate market Makwana could caused a good bit of havoc. 

Makwana worked at Fannie Mae’s data center in Urbana, MD as a Unix engineer as a contractor with a firm called OmniTech. He had root access to all Fannie Mae servers. 

The tale of Makwana malware bomb plot is a warning shot to all security teams and IT departments. Given the level of layoffs we’ve seen lately the ranks of disgruntled former employees is likely to grow. Is there any company NOT lopping off a big chunk of its workforce? And some of these workers may even have Makwana’s access privileges and knowledge of the corporate network. 

Sophos’ Graham Cluley says:

As belts tighten and the credit crunch continues to hit around the world, more and more companies will be making the decision to make staff redundant. As we’ve written before, a disaffected employee could create havoc inside your organisation so make sure that appropriate security is in place.

Also seeAre you wary of the insider on the outside?

Indeed, Makwana had intended to do some serious damage such as “destroying and altering all of the data on all Fannie Mae servers.” That quote puts it mildly. According to the initial complaint against Makwana, the former contractor’s virus “would have caused millions of dollars of damage.” Anyone that logged into the Fannie Mae network on Jan. 31 would have seen a message “Server Graveyard.”

Details of Makwana’s alleged plot surfaced in a complaint that was initially sealed to protect the identity of Fannie Mae. In the complaint, Fannie Mae is referred to as “ABC,” but defined as an outfit that facilitates mortgages. In a sworn statement, FBI agent Jessica Nye outlined the following:

Luckily, the Fannie Mae server scripts were returned to normal before mortgage chaos ensued. But the errors listed in the complaint are clear. The biggest problem: Makwana’s access wasn’t terminated when he was. He had access to Fannie Mae servers longer than he should have. 

Here’s a look at the notable excerpts of the complaint. As you can see there were warning signs and mistakes made along the way. Emphasis is mine. 

 

So far so good right? Makwana screwed up, was terminated and had to turn in his gear and access privileges. 

Well that last part didn’t go so well. 

The good news is that Makwana’s access didn’t go on indefinitely. I’ve known more than a few people that could access their former employer’s network for months after they left the company. 

However, catching Makwana’s script was really a function of luck.

There was also some good detective work too–the complaint details Makwana’s techniques and script set-up–by the Fannie Mae security team. However, a lot of work could have been avoided if only Makwana’s privileges were terminated when he was.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic.

Disclosure

Larry Dignan

Larry Dignan has nothing to disclose. He doesn’t hold investments in the technology companies he covers.

Biography

Larry Dignan

Larry Dignan is Editor in Chief of ZDNet and SmartPlanet as well as Editorial Director of ZDNet's sister site TechRepublic. He was most recently Executive Editor of News and Blogs at ZDNet. Prior to that he was executive news editor at eWeek and news editor at Baseline. He also served as the East Coast news editor and finance editor at CNET News.com. Larry has covered the technology and financial services industry since 1995, publishing articles in WallStreetWeek.com, Inter@ctive Week, The New York Times, and Financial Planning magazine. He's a graduate of the Columbia School of Journalism and the University of Delaware.

For daily updates, follow Larry on Twitter.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
52
Comments

Join the conversation!

Just In

RE: Fannie Mae IT contractor indicted for planting malware; Mortgage giant didn
kamagra 26th Feb 2010
Kamagra is a generic version of Viagra. Generic
Viagra is a drug that contains the same active
ingredient of Viagra, which is sildenafil
citrate, but is marketed under different brand
buy kamagra and
the M-1965 Field Jacket, also known as the
m65 field
jacket is a popular field jacket designed
for the U.S. military.
0 Votes
+ -
Must Have Been A Windows Network
itanalyst2@... 29th Jan 2009
Typical boot camp MCSE mentality.
0 Votes
+ -
Message has been deleted.
n0neXn0ne Updated - 29th Jan 2009
.
0 Votes
+ -
Then post something useful.
0 Votes
+ -
Why should he let facts get in the way of his trolling?
Hallowed are the Ori 29th Jan 2009
Stupid is as stupid does.
0 Votes
+ -
Windows server.
RobertMoore12@... 29th Jan 2009
NO!!! The story plainly says UNIX.
0 Votes
+ -
In this case...
Marty R. Milette 1st Feb 2009
Typical Linux boot camp mentality.

As the Linux geeks always like to say -- RTFM -- or, in this case -- READ THE F'ing Article...
0 Votes
+ -
Remind me not to hire itanalyst2
Dr_Zinj 2nd Feb 2009
Reading comprehension level appears too low.
They must implement a HR Policy that require that every employee or contractor must not have root access to their servers. Implement rigurously procedures that require every change from a development environment to production must be aproved, like when IT deploys new software releases. And remove/block or change password to those user accounts that those employees or contractors doesn?t works any more.

Also, define IT policies in their contract.
0 Votes
+ -
They do
letranger66 30th Jan 2009
A lot of what you mention is in place, contractually at least, and there are rigorous background checks. I represent a firm that is under contract with Fannie Mae.

I must say though, that working for various clients where my employees have high level server access, the inconvenience of password resets seems small in comparison to the potential damage a rogue consultant could cause.
0 Votes
+ -
Gee -- that'd work REAL GOOD...
Marty R. Milette 1st Feb 2009
Yep, don't give ANYONE root access.

Of course that would make it somewhat more difficult to maintain the servers -- wouldn't it?

As for changing accounts -- don't get your hopes up their either. There are PLENTY of 'service' accounts that most administrators know the credentials to -- in addition to 'extra' back-door accounts that would be created between the time the pink slip hits the desk and the a$$ is out the door. (If not before.)

The ONLY way to be sure is to force an immediate account audit and change the passwords for EVERY account on the system.

Relatively easy for the user accounts, but not so much fun for the service accounts and applications/roles.
I guess that one UNIX engineer didn't revoke the contractor's privileges. Don't put him on a holier-than-Microsoft pedestal just yet...
0 Votes
+ -
LDAP is a pain to setup and maintain...
rdiekema@... 29th Jan 2009
so it can be time consuming to revoke privileges in an organization that doesn't have centralized access control or a poorly maintained one.
0 Votes
+ -
Even so...
mejohnsn 29th Jan 2009
this incident proves that every responsible IT organization will bite that bullet and live with the 'pain' of setting up LDAP rather than risk a repeat of this Fannie-Mae near disaster.
0 Votes
+ -
That's what it sounds like.
zclayton2 30th Jan 2009
You would think that SOP for termination of an employee/contractor of this type would be:
Determine termination.
Setup access termination.
Coordinate schedule.
Execute termination of emplyee and access at the same time.

Codify this. It would save a lot of people from poor choices and legal fees.
0 Votes
+ -
Fannie Mae is not in the stone age
nadofurtado 31st Jan 2009
give me a break, do you really think Fannie has no LDAP? Centralized access? Long before the govt took over, Fannie came under the watchful eye of SOX and Security audit; and LDAP was in place even long before that.
Quite honestly, the focus and spin of this article seems a bit out-of-focus and sensational. I would love to read less preaching about the "devils inside your company, waiting to destroy your business", and have a larger conversation about outsourcing, IT management practice, and business strategies that rely heavily on technology.

But then again, this is ZDNet; let the terror reign on.
0 Votes
+ -
Change Management
IanF 29th Jan 2009
LoL, Jhampton. You'll need to go over to an ISACA or ISC2 forum for that kind of discussion. Obviously Fannie Mae's IT department has some lax change management policies if a contract Unix Engineer can make modifications straight to a prod box. I guess ZDNet has to consider their audience, though, and dumb it down a bit. happy
0 Votes
+ -
Government run (imagine that)...
Christian_<>< 29th Jan 2009
The Government is great at wasting tax dollars, allowing ANYONE access to critical systems.....

And imagine it being Fannie Mae cooked up from the Democrats who led this disaster into meltdown...

Now with our new socialist dictator he will lead us into tax heaven.
  • Flagged
0 Votes
+ -
Internal Threats
jshinn 1st Feb 2009
Despite being a business/technology lawyer, I've remained an optimist, but I try to work with clients to plan for the worst. In this regard, I usually believe people, i.e., employees, will do the right thing (it's bad Karma not to, right?). But I know that they won't always do the right thing, as illustrated by this post, which, coincidentally, fit in as a perfect example for my post: http://jshinn.wordpress.com/2009/01/31/preventing-data-breaches-on-the-cheap/. Thanks.
0 Votes
+ -
This kind of stuff is VERY real...
Marty R. Milette 1st Feb 2009
I've been in the position of having to axe four sys admins in the last 10 years -- and out of the four, THREE of them tried to sabbotage the network -- either before they left or after.

The odds are NOT in your favor.
0 Votes
+ -
I'edfmrr Jill my cat does linux.
rtirman37@... 29th Jan 2009
Glad that is over.
0 Votes
+ -
End of the day?
jshaw4343 29th Jan 2009
He had to the end of the day to turn in his equipment? The problem is not that they waited until late in the day to remove his access - they let the guy go back to his desk for 3 hours after announcing his termination. Terminated employees must be escorted from the building.
while doing their exit interview.

We then help them collect their things and send them out the door.

If we even think they may know something about anything, we change it.

This was just a foolish move on Omitech's part.
0 Votes
+ -
so that the unique global Id can be disabled in a moments notice and replicates/syncs to all mainframe, server, vpn, exchange accounts within minutes. At least that's the way it worked at my previous employer. It was nice for us users, because corp security policy required password changes every 30 days. With one global id, you could change the password at domain logon and within a few minutes, all your mainframe, network, vpn, and server accounts as well as Outlook exchange were all updated with the same password. When someone is terminated, a quick call by a manager to security to disable the global id and all access to all systems was immediately disabled. After the exit interview, person is escorted to desk to pack personal items and out the door, with no badge or ID.

Back in the mid 80's, I was a contractor at a mainframe shop that was downsizing a dozen or so employees (not my project). They called a "meeting" for those people to give them the "news". While they were all in a meeting, empty boxes were placed at each one's desk. During the meeting their logon ids were disabled. After the meeting, each person was escorted to their desk, packed personal stuff, and then escorted by building security to the door.

Management blew it on their allowing this guy to be around for any time at all after notice was given.
0 Votes
+ -
Not necessarily in this case
RationalGuy 29th Jan 2009
It's unclear whether this guy had the root password or privileges to sudo as root. When a guy with the root password is terminated, the only way to fix the situation is to change the password.

Centralized management wouldn't have solved this problem necessarily.
0 Votes
+ -
We remove priviledges first
sholleran 29th Jan 2009
Once the decision is made, rights are cut off and often the employee is calling tech support to find out why they cannot logon when they are asked to speak with their manager (with the ever ominous, "and bring your laptop and badge with you") - by the time the exit interview is done, they are given a box with any personal effects and depart with security. If the manager likes them, they'll get a CD burned of anything personal on the hard drive (photos, etc) as they go.

But of course, when it's tech support getting cut, everybody immediately has to rotate passwords on the servers, too.
0 Votes
+ -
Same here...
Hallowed are the Ori 29th Jan 2009
You will be called to the HR office where two armed guards will be present. You are then informed of your termination and processed out. HR then calls IT to notify them of the termination so they can remove all access permissions and secure any data present.

Meanwhile, the guards escort you back to your desk to collect any personal effects, and you are then escorted out the front door.
Right they were UN*X based scripts. Regarding WHEN they terminated his access, all I can say is that I'm sure that process will be 'under review.'.
Regarding his malicious intent, while many of us here have gone through this (whether we screwed up OR not) and can identify with how he feels, frankly what he did was an act of violence. Too bad for him. He's not only ruined his chances of ever working in the IT world again, he has also probably gotten himself landed in jail.
We all screw up. Sometimes we have to pay for it. Perhaps the best advice comes out of the Bible:
http://bible.cc/romans/12-19.htm
"Do not take revenge, dear friends, but leave room for God's wrath. For it is written, "Vengeance belongs to me. I will pay them back, declares the Lord.""
-S
0 Votes
+ -
Never wait till you last day!
tlwalker1962@... 29th Jan 2009
See, this is why you plant your malicious code, using your boss?s login, just after your 30day review. You never wait till your last day!

Of course I, myself, would never do such an evil thing.
0 Votes
+ -
Malware?
juantar 29th Jan 2009
Malicious code? ha! this could have been avoided if they were using super-secure Unix or Linux... Oh wait... Never mind...

This proves that you can write malicious code in any platform not just Windows. Not that anyone is saying that in this post, but I have seen the above argument on other posts.

A system's security is as good as the admin.
(Insert flame war below...)
0 Votes
+ -
Point made
Cayble Updated - 29th Jan 2009
All we hear is the crying about how insecure Windows is and how people are bringing Windows boxes into repair shops by the truckload to get the malware cleaned out. Common sense would surly indicate that if Windows machines were getting infected at the rate the MS nay sayers claim, half the world would have half their computers inoperable and there would mostly be nothing but ongoing chaos in the Windows networks of the world. And thats just not anything like the way it is.

It seems most of the damaging attacks we hear of are attacks not so different then this, and no network or system is immune to these kind of attacks, no matter what the OS, if there are not sufficient security policies in place or unless there is an idiot at the switch who just has no sense.
0 Votes
+ -
Re Point made
vilppuu@... 1st Feb 2009
"It seems most of the damaging attacks we hear of are attacks not so
different then this, and no network or system is immune to these kind
of attacks, no matter what the OS, if there are not sufficient security
policies in place or unless there is an idiot at the switch who just has
no sense"

NOT TRUE!!!!
I am curious. Generally speaking, most of those viruses, malware and
trojans out there are no where near as dangerous as an evil
intentioned IT technician with the keys to the code vault and system
hardware. This situation has nothing to do with the ongoing campaign
to compromise personal PCs. I am just wondering what if an IT
technician goes "postal" with code. That would be one hell of a mess.
0 Votes
+ -
It's similar
AndyCee 29th Jan 2009
With finance, or even management. The security of how things are managed is largely determined by the one doing the managing. The real difference is that this could be scheduled to execute after he left.

If it were an outside attack, that's a different type of security.
0 Votes
+ -
SHOCKER! - Democrat ran Fannie Mae disaster
Christian_<>< 29th Jan 2009
Welcome to a corrupt Congress Democratic led and they are the ones responsible for the entire housing debacle forcing banks to give out loans to everyone...

Now with our Socialist leader he will lead all comrades to a state of union and control we have never seen before....


sad
0 Votes
+ -
ROFL!
0 Votes
+ -
...on two words.

Democrat socialist (skip) democrat socialist (skip) Democrat socialist (skip) and so on and so on ad nauseam.

Maybe next year he'll learn some new words...although I won't hold my breath waiting for that to happen. The incredibly narrow-minded aren't open to learning much willingly. For instance, he'll never acknowledge that the CRA was intended to prevent discrimination and red-lining in lending practices. The CRA never said "Loan money to anyone regardless of their inability to pay." And the CRA didn't create "no doc" loans. Bankers did.
0 Votes
+ -
Who's Fannie Mae be at risk here?
bobmatch@... 31st Jan 2009
Why are we taking this computer security subject blog and using it to stand on a soap box? Besides we all know who's watch the Eco. broke down on. Move on! Learn the lessons here, in the coming months we'll see more of this kind of behavior if not careful to follow good firing practices. Other pieces of our infrastructure can also be at risk as we spiral down.
0 Votes
+ -
Like my Daddy used to say
dev-null 27th Feb 2009
All Republicans aren't idiots, but somehow all idiots are Republicans.
Looking at some of the snippets from the original complaint, what I'm more concerned about is that the article's author seems to have included the internal Fannie Mae server names in this publicly available article. Shouldn't this have been scrubbed before disseminating for public consumption? I'm guessing if Fannie Mae hasn't changed these server names, this is something their internal security team might have a problem with.
0 Votes
+ -
Is my personal information safe?
DAvenger 29th Jan 2009
Given that he had 'root' access to these servers, and the gonads to plant this time bomb, then I would highly suspect that he has made off with all the personal information in the databases he had access to. So if I had a Fannie Mae mortgage, is my personal information safe anymore? Did my SSN, driver's license, home phone, address, and everything else get stolen and sold by this criminal?
Prat !!!
I see that Comical Ali is alive and spamming the yanks in their tanks.

Fannie May sub-primed under two terms of REPUBLICAN mismanagement.

Park your rubbish elsewhere; this is a technical thread.
0 Votes
+ -
Does the Press Understand Computers?
jabailo1 30th Jan 2009
For all the "tech reporting" on this story, the
descriptions of exactly what his "script" did were
really vague or unbelievable.

For example, one story said that the script would set
all files on the disk equal to zero?

Since he was administering databases, was that
supposed to mean that he was going to set the value of
all numeric data to zero with a sql UPDATE? Or that
he wrote a low level virus that set all the bits to
zero? No one seems to know!

Then his script "locked access". So, does that mean
it would change the root password?

And then it said it would erase things. What?
Files? Programs? The OS? Wipe the hard disk?

Lastly, what about DRM (Data recovery)? Wouldn't the
Feds have one if not two back up systems that could be
recovered from backups and located in different parts
of the county? My business does that all the time --
create DRM systems.

Bottom line: does anyone in the Computer press know
anything about Computers ?!?
You make good point Terry. Hopefully Fannie Mae and the outside contractor can come to that same conclusion. People have no clue what kind of information can be retrieved with a customer information file...SSN, Credit Card, Address, Phone, Accounts and the list goes on. I'm sure someone would pay a substantial sum for that information since credit card scams are at an all time high.
This is why Change Management and Configuration Management are so important. Management should be auditing systems and ensuring that controls, checks and balances are ACTUALLY IN PLACE and not just being given "lip service." Unbelievable that changes could be made on scripts without notice.

How about using some Host Intrusion Detection systems that would have indicated to all the the baseline had changed, even though it was apparently done in the development network. Moreover, how was it that the development network and production network were connected in such a way that a script on the development network could execute on the production network?

Although there are a lack of details indicating how the channel was established to the production network, if the system was not hacked to establish a backdoor connection to the production network, there was a serious breach and lack of of security controls.The Development network should not be connected to the production network as we all know.

-Herb
Access to some systems cannot be removed in real time. Standard protocol for terminating a contractor or employee is you take their laptop while you are firing them. Why in the world would any manager tell someone they are fired (after 2 years) and then let them hang around working for another2 hours? I happen to know that this protocol is firmly embedded in FM process, so either this article is inaccurate or someone else needs to get fired.
0 Votes
+ -
The FBI agent who wrote the complaint shown in the article apparently doesn't understand computer systems well. There appear to be some basic misunderstandings. For example, the first sentence in the portion shown is, ?Any ABC data that was not restored prior to this malicious script executing would be lost.? I think she means, ?Any ABC data that was not backed up...?
That's why you should be careful who you piss off. I would think anyone who is a sysadmin would have the capability to hose the system if they really wanted to, so you should be very careful who you give this access to and the circumstances of their employment.
I have to say that I agree, the guy you have to watch out for is the one who has been waiting for the last day for a long time and has several plans in place and has had plenty of time to get hooks in several places. The guy that got caught is obviously a rookie, he could have erased the log file(s) or substituted others etc. especially if he had root access.
Even at my little dinky company, we have a documented step by step procedure for employee termination as well as outside contractor computer access. Nobody, I mean nobody gets the root password for our BSD servers or the Administrator password for our PDC. Temporary accounts with just enough priveledges to accomplish the tasks are made and removed as soon as they are no longer needed, anything that really really requires root/administrator access is done in house or the contractor is constantly monitored. Admittedly this is much easier in a small company but thats just what has to be done, too many sneaky, unscrupulous people out there.
Kamagra is a generic version of Viagra. Generic
Viagra is a drug that contains the same active
ingredient of Viagra, which is sildenafil
citrate, but is marketed under different brand
buy kamagra and
the M-1965 Field Jacket, also known as the
m65 field
jacket is a popular field jacket designed
for the U.S. military.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix