HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
NewEraCracker
LOIC
C#2010–2010
NewEraCracker / LOIC · Archived

LOIC

Deprecated - Low Orbit Ion Cannon - An open source network stress tool, written in C#. Based on Praetox's LOIC project. USE ON YOUR OWN RISK. WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. IF YOU GET V& IT IS YOUR FAULT.

2Distinct people
2Mentions
0Explicit recommenders
3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Deprecated - Low Orbit Ion Cannon - An open source network stress tool, written in C#. Based on Praetox's LOIC project. USE ON YOUR OWN RISK. WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. IF YOU GET V& IT IS YOUR FAULT.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2010-12-08 21:16:59 UTC to 2010-12-09 17:21:36 UTC.

012010-12-08 21:00:00 UTC to 2010-12-08 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 8, 21:002010-12-08 22:00:00 UTC to 2010-12-08 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-08 23:00:00 UTC to 2010-12-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 00:00:00 UTC to 2010-12-09 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 01:00:00 UTC to 2010-12-09 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 02:00:00 UTC to 2010-12-09 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 03:00:00 UTC to 2010-12-09 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 04:00:00 UTC to 2010-12-09 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 05:00:00 UTC to 2010-12-09 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 06:00:00 UTC to 2010-12-09 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 07:00:00 UTC to 2010-12-09 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 9, 07:002010-12-09 08:00:00 UTC to 2010-12-09 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 09:00:00 UTC to 2010-12-09 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 10:00:00 UTC to 2010-12-09 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 11:00:00 UTC to 2010-12-09 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 12:00:00 UTC to 2010-12-09 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 13:00:00 UTC to 2010-12-09 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 14:00:00 UTC to 2010-12-09 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 15:00:00 UTC to 2010-12-09 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 16:00:00 UTC to 2010-12-09 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-12-09 17:00:00 UTC to 2010-12-09 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 9, 17:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 8, 21:002010-12-08 21:00:00 UTC2010-12-08 22:00:00 UTC101
Dec 8, 22:002010-12-08 22:00:00 UTC2010-12-08 23:00:00 UTC000
Dec 8, 23:002010-12-08 23:00:00 UTC2010-12-09 00:00:00 UTC000
Dec 9, 00:002010-12-09 00:00:00 UTC2010-12-09 01:00:00 UTC000
Dec 9, 01:002010-12-09 01:00:00 UTC2010-12-09 02:00:00 UTC000
Dec 9, 02:002010-12-09 02:00:00 UTC2010-12-09 03:00:00 UTC000
Dec 9, 03:002010-12-09 03:00:00 UTC2010-12-09 04:00:00 UTC000
Dec 9, 04:002010-12-09 04:00:00 UTC2010-12-09 05:00:00 UTC000
Dec 9, 05:002010-12-09 05:00:00 UTC2010-12-09 06:00:00 UTC000
Dec 9, 06:002010-12-09 06:00:00 UTC2010-12-09 07:00:00 UTC000
Dec 9, 07:002010-12-09 07:00:00 UTC2010-12-09 08:00:00 UTC000
Dec 9, 08:002010-12-09 08:00:00 UTC2010-12-09 09:00:00 UTC000
Dec 9, 09:002010-12-09 09:00:00 UTC2010-12-09 10:00:00 UTC000
Dec 9, 10:002010-12-09 10:00:00 UTC2010-12-09 11:00:00 UTC000
Dec 9, 11:002010-12-09 11:00:00 UTC2010-12-09 12:00:00 UTC000
Dec 9, 12:002010-12-09 12:00:00 UTC2010-12-09 13:00:00 UTC000
Dec 9, 13:002010-12-09 13:00:00 UTC2010-12-09 14:00:00 UTC000
Dec 9, 14:002010-12-09 14:00:00 UTC2010-12-09 15:00:00 UTC000
Dec 9, 15:002010-12-09 15:00:00 UTC2010-12-09 16:00:00 UTC000
Dec 9, 16:002010-12-09 16:00:00 UTC2010-12-09 17:00:00 UTC000
Dec 9, 17:002010-12-09 17:00:00 UTC2010-12-09 18:00:00 UTC101

What Hacker News says

2 sources
The source for one version of LOIC can be found on GitHub: https://github.com/NewEraCracker/LOIC/ A quick skim-read of the code mentioned in the post shows that this version seems to be different, specifically: https://github.com/NewEraCracker/LOIC/blob/master/HTTPFloode... if (random == true) buf = System.Text.Encoding.ASCII.GetBytes( String.Format("GET {0}{1} HTTP/1.1{2}Host: {3}{2}{2}{2}", Subsite, new Functions().RandomString(), Environment.NewLine, Host)); else buf = System.Text.Encoding.ASCII.GetBytes( String.Format("GET {0} HTTP/1.1{1}Host: {2}{1}{1}{1}", Subsite, Environment.NewLine, Host)); (botched indentation is my own) The Host header mentioned in the blog post is present, the protocol is now HTTP/1.1 and random string appears to be an attempt to defeat a simple pack
Read the rest
et matching algorithm. I doubt many legitimate requests these days come without a User-Agent header, though...
In Possible flaw in LOIC - Tool used to DDoS Amazon
This is a confirmed target of "Operation Payback," a 4chan/Anonymous attack against those who have opposed Wikileaks. The primary targets include MasterCard (which was hit earlier today) and Visa, who refused to process donations to Wikileaks. The Swedish Prosecution authority is apparently also on the list. Although these types of DDoS attacks (they are using the Low Orbit Ion Cannon tool available at https://github.com/NewEraCracker/LOIC/ ) do not affect cardholder data, it will render legitimate users completely unable to login to their merchant accounts.
In Visa is under DDoS attack

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.