Anonymous hacks Federal Reserve, data compromised


Recommended Posts

After Anonymous posted sensitive credentials of over 4,600 banking executives to a government Web site on Super Bowl Sunday, the Federal Reserve acknowledged the attack in a Tuesday morning statement to affected individuals and press.

However, while a spokesperson from the Federal Reserve told The Huffington Post that Anonymous' claim to the hack's importance was "overstated," information security professionals that serve financial institutions are saying the exact opposite?and are not best pleased with the Federal Reserve.

ZDNet has now learned that the compromised and exposed database belongs to The St. Louis Fed Emergency Communications System.

post-76181-0-69622700-1360182877.jpg

Source: http://www.zdnet.com...ach-7000010902/

Wow! Seems like Anonymous is doing some damage to US government sites. Wonder how the Pentagon "Cyber Command" is going to respond. (thanks torrentthief)

While I definitely don't hold much sympathy for bankers or the Federal Reserve, I have to ask how this hack relates to "the reform of computer laws" or investigation into Aaron Swartz's prosecution. Seems like this is more related to Occupy-type protest.

post-76181-0-69622700-1360182877.jpg

Source: http://www.zdnet.com...ach-7000010902/

Wow! Seems like Anonymous is doing some damage to US government sites. Wonder how the Pentagon "Cyber Command" is going to respond.

The federal reserve isn't run by the government, it is a private organisation, it is pure evil.

The federal reserve isn't run by the government, it is a private organisation, it is pure evil.

You're right. I thought I paid attention in my Eco/Gov class, guess not. :p

The government Web site, which was compromised and used to post the spreadsheet, The Alabama Criminal Justice Information Center, did not respond to requests for comment from the Washington Post.

The page?with URL filename "oops-we-did-it-again"?remained accessible into early Monday morning PST. A cached version of the page was still available as of Tuesday afternoon, as well as a copy of the raw text placed on Pastebin at the time of the attack.

Anyone bother reading the article. Anonymous should be jailed, they are farking around with our economy.

http://www.federalreserve.gov/

Anyone bother reading the article. Anonymous should be jailed, they are farking around with our economy.

http://www.federalreserve.gov/

What they(Anon) need to do is actually collapse our economy completely. Maybe that will start the change that we desperately need.

  • Like 2

The federal reserve isn't run by the government, it is a private organisation, it is pure evil.

Well all I see is both sides of the coin are the devil, because the Federal Governement is evil too. Just remember, it was our governmet officias who went behind closed doors and signed the deal with th devil. WHat is so funny, is the USA faught in a revolt to end Bristish stronghold, only to sell out to them and others by allow them to control our money. When you dont control your own money than you have a serios problem.

The only way the USA could get out of debt with the FRB is to make its own money, make its own bank to back it up which is easy as they could have these corps provide the capital and use that money to pay off the debt little by little but dont borrow anymore.

Anyone bother reading the article. Anonymous should be jailed, they are farking around with our economy.

http://www.federalreserve.gov/

The logo is interesting, except 9/11 wasn't terrorism. It was our own government insatible appetitite for war.

Well all I see is both sides of the coin are the devil, because the Federal Governement is evil too. Just remember, it was our governmet officias who went behind closed doors and signed the deal with th devil. WHat is so funny, is the USA faught in a revolt to end Bristish stronghold, only to sell out to them and others by allow them to control our money. When you dont control your own money than you have a serios problem.

The only way the USA could get out of debt with the FRB is to make its own money, make its own bank to back it up which is easy as they could have these corps provide the capital and use that money to pay off the debt little by little but dont borrow anymore.

Maybe your Federal Government is evil.

The logo is interesting, except 9/11 wasn't terrorism. It was our own government insatible appetitite for war.

Take your conspiracy BS to the proper section.

lolll you really think all of them are script kiddies ?

Btw, the federal reserve are the one responsible for the ****ty economy that you have. You clearly have NO clue how they operate.

<Snipped>

Edited by Anaron

What they(Anon) need to do is actually collapse our economy completely. Maybe that will start the change that we desperately need.

...or catalyst the change they are actually planing, I'm sure 'they' known money has no actual value, in the end, general population suffer the most, as always.

Blaming your president(s) for the countries debt is also getting old.

The President, in accordance with to the Budget and Accounting Act of 1921, must submit a budget to Congress each year

Then Congress reviews it to make sure the current laws on mandatory spending are met.

Then Who or Whom is to blame? If it is the President that creates the budget?

Just a simple question:

If the President created it then isn't it that person to blame?

The federal reserve isn't run by the government, it is a private organisation, it is pure evil.

Who owns the Federal Reserve?

The Federal Reserve System fulfills its public mission as an independent entity within government. It is not "owned" by anyone and is not a private, profit-making institution.

http://www.federalre...about_14986.htm

1/2 right and yes some might say it is evil....

Originally it was created to help stop banks from going under... Such that happened in the early 1900's (I think 1907) when people wanted their money and there was no money to give out. So some small banks went out of business and people lost their money.

What they do now is a shame adjusting rates at random. The only good thing is they insure deposited money is made available to a person to withdraw no matter what. (but only to a certain limit)

http://www.federalre...about_14986.htm

1/2 right and yes some might say it is evil....

Originally it was created to help stop banks from going under... Such that happened in the early 1900's (I think 1907) when people wanted their money and there was no money to give out. So some small banks went out of business and people lost their money.

What they do now is a shame adjusting rates at random. The only good thing is they insure deposited money is made available to a person to withdraw no matter what. (but only to a certain limit)

And only to a certain few.

And only to a certain few.

Yes if the bank you bank at is FDIC insured.

They are not a bank for people but a bank for banks... and a bank where banks can get loans from they are supposed to make available to people. Which helps to stagnate or push the economy forward or drive it into the ground.

Yes if the bank you bank at is FDIC insured.

They are not a bank for people but a bank for banks... and a bank where banks can get loans from they are supposed to make available to people. Which helps to stagnate or push the economy forward or drive it into the ground.

Drive it into the ground is 100% correct. But oh well, The US doesn't have a pot to pee in or a window to throw it out.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!