Showing posts with label Assange. Show all posts
Showing posts with label Assange. Show all posts

Monday, June 24, 2019

Trump-Russia Collusion Narrative Destroyed

Hope Hicks testified, in full, before the House Committee,
answering all questions regarding Trump's contact with Russia.
The Democrats now focus solely on questions she declined
which addressed other White House issues.



Since the News Media buried this report, 
hoping the voting public would not notice, 
we are re-publishing it, as written, 
to give it global coverage and offset the 
Fake News the Democrats' are reporting.  

True journalism is rare today, so we want to 
give it our full support and widest distribution!




While the press portrayed Hope Hicks’s silence as all-inclusive, 
in reality she testified at length and in detail about all aspects of 
Trump’s presidential campaign. 


How Hope Hicks’s Testimony Destroyed The Trump-Russia Collusion Narrative.
The Federalist, 24June2019
By: Margot Cleveland 

Following the Thursday [13June2019] release of the transcript from Hope Hicks’s testimony before the Democrat-controlled House Judiciary Committee, the media quickly concentrated on the questions Trump’s former communications director refused to answer.

But while the press portrayed Hicks’s silence as all-inclusive, in reality Hicks testified at length and in detail about all aspects of Donald Trump’s presidential campaign. And that testimony established yet again that the Russia collusion narrative was a hoax. 

One theme of Democrats’ questioning of Hicks concerned the Trump campaign’s contacts with Russians. Several times Hicks confirmed the lack of contacts between top Trump campaign members and Russia.

 “I’m telling you,” Hicks testified, “I wasn’t aware in the campaign of any contacts with Russian officials.

Later, when asked again what, if any, communications and contacts there were between the Trump campaign and Russian or Russian officials, Hicks noted that during the campaign she wasn’t aware of any but later learned of insignificant contacts, such as Jeff Sessions meeting the Russian ambassador at a foreign policy speech.

Hicks further testified that a Russian official’s post-election comment that Russia was “in constant communication or constant contact with members of Trump’s inner circle throughout the campaign,” “was not true.”

I’m not aware of anybody that regularly interacted with Mr. Trump that was a decisionmaker that advised him on a frequent basis that had, ‘regular contacts’ with any Russian officials,” Hicks stressed.

Hicks, who had previously worked for the Trump organization, also testified that she was not aware of any financial ties between Russia and the Trump Organization during the campaign. Nor did Hicks have any knowledge of any “foreign government providing cash or any other thing of value to Mr. Trump during the campaign,” or of any conversations during the campaign about Trump traveling to Russia (other than for the Miss Universe Pageant), or meeting with Russian President Vladimir Putin.

Hicks further told the committee that she only “became aware that the Russian government was attempting to interfere in the 2016 elections” when the story hit the press.

Nothing on the DNC Hack Or Trump Tower 

Democrats on the Committee nonetheless pushed the Russia collusion narrative by attempting to portray an email Hicks received from the editor-in-chief of the Russian internet newspaper Vzglyad as evidence of a Russian conspiracy.

Joe Neguse
Democratic Representative Joe Neguse flipped to the much-referenced Robert Mueller report to read the special counsel’s finding that “one day earlier the publication’s founder and former Russian parliamentarian Konstantin Rykov had registered two Russian websites, Trump2016.ru and DonaldTrump2016.ru.

But Neguse’s attempt to implicate the Trump campaign in Russia’s online efforts to interfere in the election failed badly.

Hicks noted: “I don’t recall receiving the interview request”; I received hundreds of interview requests, sometimes daily.

Because Trump had no intention of participating in the interview, Hicks explained, she was not concerned about the identity of the outlet, and hadn’t even realized until after the fact that the email had come from a Russian.

Concerning the WikiLeaks hacks, Hicks made clear that the only discussion the campaign had was “...speculation about if there would be more emails or information released, but that was prompted by things in the media” and it wasn’t with certainty that more leaks would happen, but “with speculation and skepticism.”

No” Hicks stressed, Trump did not talk about WikiLeaks or the hack, nor did anybody else in the campaign, other than what was discussed in the public domain. Hicks also testified that during the campaign she had heard nothing about Roger Stone and his supposed relationship with WikiLeaks or its founder Julian Assange, or about WikiLeaks’ “divulgence of information about the emails of Hillary Clinton and Mr. Podesta” beyond media coverage.

In short, Hicks stated that during the campaign, Trump never indicated that he knew ahead of time that WikiLeaks was responsible for the Democratic National Committee hacks or that he had knowledge that additional information would be released.

Hicks also confirmed that before the election she had not been told that anyone at the Trump campaign had been offered information about Hillary Clinton.

The Trump Tower meeting was another focus of committee questions:
Hicks told the committee that she did not know about the Trump Tower meeting or Donald Trump Jr.’s emails about that meeting until after Trump was elected president. She had also never heard “... any discussion from any Trump Organization employee or Mr. Trump about an ongoing effort to pursue a potential Trump Tower Moscow at that time...” another thread woven into the Russia collusion hoax.

Hick’s responses during last week’s hearing also provided fresh insight into Trump’s behind-the-scenes response to news of Russian interference. Hicks noted that the campaign only “... became aware that the Russian government was attempting to interfere in the 2016 elections...” when the story hit the press. The president’s former confidant added that any conversations she was privy to during the campaign concerning Russia interference in the election mirrored what Trump said publicly.


The Trump Collusion Narrative Is a Red Herring 

Then, when asked what specifically Trump said during the campaign about public reports that his team was coordinating with Russia, Hicks relayed that Trump called it “nonsense.”

Trump believed that the Russia collusion conspiracy “...was something that the Clinton campaign had made up to deflect from the information that they viewed as harmful to their candidate, to their campaign...” Hicks explained.  She also testified that she agreed with his assessment and that the “... unsubstantiated claims that [the Trump campaign] were coordinating with Russia was an attempt to distract and deflect.

Trump's former communications director added that the Trump campaign obviously knew there was no collusion, but admitted that had she been working instead for the Clinton campaign, she “probably would have taken a similar strategy.”

Hicks further noted that, whether the Russia collusion hoax was being peddled by the “Clinton campaign or speculated about in the media,” her discussions with candidate Trump focused on how to respond to the false claims.

Hicks also shared details of her conversation with Trump following his late-July 2016 off-the-cuff remark:
Russia, if you’re listening, I hope you’re able to find the 30,000 emails that are missing. I think you will probably be rewarded mightily by our press.”

Hicks explained that she informed Trump that “... some in the media had taken the expression quite literally, and that they were concerned he was encouraging foreign governments to, you know, locate those emails, and that that was obviously something that the media felt was extremely inappropriate and demanded a response from Mr. Trump and the campaign as to what exactly he meant by that.

Hicks stated that, “... both from Trump’s remark and her discussion with him after,” she understood the comment as a joke. When pushed about what Trump had said, Hicks conveyed that he noted
it was intended as a light-hearted comment.

Trump Was Concerned About Paul Manafort 

In practice, however, Trump took concerns about Russia’s meddling seriously, Hicks explained.


Paul Manafort
For instance, according to Hicks, after the media began questioning Trump’s campaign chair, Paul Manafort. Trump, not realizing
Manafort’s close relationship with Richard Gates, asked Gates to keep an eye on Manafort.

Trump questioned some of Manafort’s “past work with other foreign governments, foreign campaigns...,” and stressed that “none of that would be appropriate to be ongoing during his service with the Trump campaign...” Hicks elaborated. He also asked Gates to let him know “if anything led him to believe that was ongoing.”

Mike Flynn
When, following Trump’s election, then-President Barack Obama raised questions about Michael Flynn to Trump, Hicks explained that warning tainted Trump’s view of Flynn going forward.

Trump “... was a bit bewildered that, you know, of all the things that the two of them could have been discussing,” it was Flynn that came up.

(This detail also raises the question of Obama’s motivation and his efforts to sour the president-elect’s relationship with Flynn.) 

Hicks’ testimony also negated several other Democratic and media talking points on Russia interference and collusion. While Democrats attempted to portray Trump as unperturbed by Russia’s interference in the 2016 elections, Hicks countered, “I think he was concerned, but I think he was simultaneously concerned that folks with a political agenda were going to weaponize that assessment to try to undermine the legitimacy of this election.

Misrepresenting the Truth for Political Gain 

Ted Lieu [CA-D]
Hicks similarly exposed how the media misrepresented information to further the Trump-Russia collusion narrative, when Representative Ted Lieu attempted to do the same during the hearing.

In 2008, Donald Trump, Jr., was quoted as saying ‘In terms of high-end product influx into the US, Russians make up a pretty disproportionate cross-section of a lot of our assets. We see a lot of money pouring in from Russia’” Lieu quoted to Hicks.

Hicks acknowledged that she had spoken with Trump Jr., about this statement, but only to ensure “the media wasn’t misrepresenting the remark or presenting it in any misleading way.”

Hicks obliterated many of the Russia-collusion talking points pushed by Democrats and the media for the last three years.

And how was the media mischaracterizing Donald Trump, Jr.’s remarks?” Lieu quizzed.

The media “made it seem like there was Russian money coming into the Trump Organization in a way that was inappropriate or somehow sinister when Trump Jr., was merely describing the kinds of clientele that were purchasing luxury apartments, both in New York City, Chicago, and in South Florida.  They’re a luxury, globally recognized real estate company,Hicks explained, so “it would be odd if [the Trump Organization] weren’t selling to people just because they’re affiliated with Russia.

By the end of her nearly eight hours of testimony last week, Hicks had obliterated many of the Russia-collusion talking points pushed by Democrats and the media for the last three years, even more expertly than Mueller did in his special counsel report.

As one Democrat noted during the hearing, Hicks was “... with [Trump] every day,” during both the primary and general election.
She would have known had the campaign colluded with Russia.
Yet her testimony made clear there was no Russia strategy, significant contact, collaboration, or collusion, which is why when Hicks was asked whether she thought the President “might be angry about [her] testifying before Congress today...
her ready reply punctuated her significant—but unreported—testimony:
I think the President knows that I would tell the truth, and the truth is there was no collusion. And I’m happy to say that as many times as is necessary today.


----------------------


Margot Cleveland is a senior contributor to The Federalist

Cleveland served nearly 25 years as a permanent law clerk 
to a federal appellate judge and is a former full-time faculty 
member and current adjunct instructor at the college of business
at the University of Notre Dame. 

The views expressed here are 
those of Cleveland in her private capacity.

Wednesday, December 13, 2017

Bogus Tax Bill Follows Bogus Alabama Election





GaryVarvel.com

click here for related story
The Post & Email
By: Ron Ewart

More news on the bogus Tax Bill process.


The RepubliCrats are seeking a way to kill it before they take their Christmas Recess, so, having succeeded with the GOP/DNC collusion to give Sessions' seat to a Democrat, the end-game now continues.

As Stalin noted:
"It is enough that the people know there was an election.  The people who cast the votes decide nothing.  The people who count the votes decide everything."



The Senate margin is now razor-thin, but, surprise -- McCain has suddenly taken ill and has taken up residence in Walter Reed Military Hospital and will be "unable" to vote on the Tax bill; that "brain cancer" thing is a terrible burden.  

We salute the good senator since most people enduring brain cancer  deteriore quickly and have long since passed away, but, he seems spry as a new rooster.  
Is it cancer, or just a deformed brain.


So, essentially, the Bill will now take one of two paths:
1) It will fail to pass because the GOP now has no clear majority
2) In order to pass, the Bill will have to undergo considerable compromise with the Democrats, and the newly unacceptable Tax Bill will be sent over to Trump for signature.

-- Either way, we lose!

Pass or not, both Parties will walk away with plenty of pork, and the tax breaks we anticipated will now be corrupted so that deductions and credits will be replaced with new scales and add-ons.  It looks as if the AMT [Adjusted Minimum Tax] has already crept back into the Bill, and we're certain many of the tax hikes buried in ObamaCare will be revived.

You jerks in Congress
screwed up my Tax Reform
The end result will be that both Parties will then attack Trump for HIS inability to get the Tax Bill through as promised in his campaign.

This will annoy the voters, and distract the voters from the current scandals implicating Schumer for his involvement in sex scandals, and the overwhelming evidence being presented indicating the absolute corruption of Deep State politicians now resigning in noticeable numbers.



Note to Congress and the Senate:
2018 is an election year, 
and we'll identify and evict you bastards who sabotaged this tax bill!


Draining the Swamp is tough business;

I'd suggest to Mr Trump that he speed up the process with a little napalm.



"I love the smell of napalm in the morning"

Tuesday, March 7, 2017

CIA Surveillance Exposed by Wikileaks


Note the original publication date of this blogpost
was 2017.

Since Assange is again under major attack, with the objective 
to ensure his incarceration and/or death, I've been asked to republish this blog post which includes significant revelations  which we can assume are included among his more recent drops from, among others, Entheos.


---------------
The original blog post follows:

Normally, we try to refine reports such as this; however, this report in its raw form 
contains so much credible information of immediate import that we will publish 
as is, with exceptional areas highlighted with bolding and color.

Very briefly, this ties in with the "wire-tapping" issue, to which we have alluded 
as a euphemism rather than actual.  Reading this report will give the 
reader a better idea of the vulnerabilities we face in using any type 
of communication; kudos again to Mr Snowden and to Mr Assange for  
introducing us to these issues and displaying both CIA and NSA's methodologies.




----------

Wikileaks Analysis


Disclosures include: 

1) CIA management by-passed encryption on phone and messaging services such as Signal, WhatsApp and Telegram.  

2) CIA hackers can penetrate Android phones and collect audio and message traffic before encryption is applied.

3) CIA can [and did] engage in “false flag” cyber-attacks to portray Russia as the assailant. 

4) The CIA’s Remote Devices Branch’s [UMBRAGE] group, collects and maintains a substantial library of attack techniques ‘stolen’ from malware produced in other state,s including the Russian Federation.


CIA malware targets iPhone, Android, smart TVs

CIA malware and hacking tools are built by EDG (Engineering Development Group), a software development group within CCI (Center for Cyber Intelligence), a department belonging to the CIA's DDI (Directorate for Digital Innovation). The DDI is one of the five major directorates of the CIA (see this organizational chart of the CIA for more details).
[ED Note
The DDI was originally the analytical division of CIA, and was highly regarded.  That function was replaced by the Digital Innovation Directorate]
EDG MALWARE OPS



The EDG is responsible for the development, testing and operational support of all backdoors, exploits, malicious payloads, trojans, viruses and any other kind of malware used by the CIA in its covert operations world-wide.




Your TV is never really off

The increasing sophistication of surveillance techniques has drawn comparisons with George Orwell's 1984, but "Weeping Angel", developed by the CIA's Embedded Devices Branch (EDB), which infests smart TVs, transforming them into covert microphones, is surely its most emblematic realization.


The attack against Samsung smart TVs was developed in cooperation with the United Kingdom's MI5/BTSS. After infestation, Weeping Angel places the target TV in a 'Fake-Off' mode, so that the owner falsely believes the TV is off when it is on. In 'Fake-Off' mode the TV operates as a bug, recording conversations in the room and sending them over the Internet to a covert CIA server.

In October 2014, the CIA was looking at infecting the vehicle control systems used by modern cars and trucks.  

[ED Note: 
Recall here the Cash for Clunkers program, forcing vehicle owners to upgrade to modern vehicles with computers which could be hacked by CIA as an auto control mechanism.





Hacked computer leaves driver with no control
The purpose of such control is not specified, but
it would permit the CIA to engage in nearly undetectable assassinations

 [There have been a number of single vehicle "accidents" causing the deaths of prominent individuals.]
[This is a personal issue since my SUV's computer stopped functioning at 70 MPH, leaving me without control of steering or brakes; fortunately a State Trooper was on the scene to assist.]

The CIA's Mobile Devices Branch (MDB) developed numerous attacks to remotely hack and control popular smart phones. Infected phones can be instructed to send the CIA the user's geolocation, audio and text communications as well as covertly activate the phone's camera and microphone.

MDB Remote Hacking of Your iPhone
Despite iPhone's minority share (14.5%) of the global smart phone market in 2016, a specialized unit in the CIA's Mobile Development Branch produced malware to infest, control and exfiltrate data from iPhones and other Apple products running iOS, such as iPads. CIA's arsenal includes numerous local and remote "zero days" developed by CIA or obtained from GCHQ, NSA, FBI or purchased from cyber arms contractors such as Baitshop. The disproportionate focus on iOS may be explained by the popularity of the iPhone among social, political, diplomatic and business elites.


similar unit targets Google's Android which is used to run the majority of the world's smart phones (~85%) including Samsung, HTC and Sony. 1.15 billion Android powered phones were sold last year. "Year Zero" shows that as of 2016 the CIA had 24 "weaponized" Android "zero days" which it has developed itself and obtained from GCHQ, NSA and cyber arms contractors.
These techniques permit the CIA to bypass the encryption of 
WhatsApp, 
Signal, 
Telegram, 
Wiebo, 
Confide  
Cloackman 
by hacking the "smart" phones on which they operate to collect audio and message traffic 
before encryption is applied!

CIA malware targets Windows, OSx, Linux, routers


The CIA also runs a very substantial effort to infect and control Microsoft Windows users with its malware hacking tools. This includes multiple local and remote weaponized "zero days", air gap jumping viruses such as 

"Hammer Drill" which infects software distributed 
 to hide data in images or in covert disk areas 







Many of these infection efforts are pulled together by the CIA's Automated Implant Branch (AIB), which has developed several attack systems for automated infestation and control of CIA malware, such as "Assassin" and "Medusa".

Attacks against Internet infrastructure and web-servers are developed by the CIA's Network Devices Branch (NDB).
The CIA has developed automated multi-platform malware attack and control systems covering Windows, Mac OS X, Solaris, Linux and more, such as EDB's "HIVE" and the related "Cutthroat" and "Swindle" tools, which are described in the examples section below.

CIA 'hoarded' vulnerabilities ("Zero Days")


In the wake of Edward Snowden's leaks about the NSA, the US technology industry secured a commitment from the Obama administration that the executive would disclose on an ongoing basis — rather than hoard — serious vulnerabilities, exploits, bugs or "zero days" to Apple, Google, Microsoft, and other US-based manufacturers.
Serious vulnerabilities not disclosed to the manufacturers place huge swathes of the population and critical infrastructure at risk to foreign intelligence or cyber criminals who independently discover or hear rumors of the vulnerability. 
If the CIA can discover such vulnerabilities so can others.
The US government's commitment to the Vulnerabilities Equities Process came after significant lobbying by US technology companies which risk losing their share of the global market over real and perceived hidden vulnerabilities. 
The government stated that it would disclose all pervasive vulnerabilities discovered after 2010 on an ongoing basis.
"Year Zero" documents show that the CIA breached the Obama administration's commitments. 
Many of the vulnerabilities used in the CIA's cyber arsenal are pervasive and some may already have been found by rival intelligence agencies or cyber criminals.
As an example, 
specific CIA malware revealed in "Year Zero" is able to penetrate, infest and control both the Android phone and iPhone software that runs or has run presidential Twitter accounts. 
The CIA attacks this software by using undisclosed security vulnerabilities ("zero days") possessed by the CIA but if the CIA can hack these phones then so can everyone else who has obtained or discovered the vulnerability. 
As long as the CIA keeps these vulnerabilities concealed from Apple and Google (who make the phones) they will not be fixed, and the phones will remain hackable.
The same vulnerabilities exist for the population at large, including the US Cabinet, Congress, top CEOs, system administrators, security officers and engineers. By hiding these security flaws from manufacturers like Apple and Google the CIA ensures that it can hack everyone at the expense of leaving everyone hackable.

Cyberwar programs are a serious proliferation risk


Cyber 'weapons' are not possible to keep under effective control.
While nuclear proliferation has been restrained by the enormous costs and visible infrastructure involved in assembling enough fissile material to produce a critical nuclear mass, cyber 'weapons', once developed, are very hard to retain.
Cyber 'weapons' are in fact just computer programs which can be pirated like any other. Since they are entirely comprised of information they can be copied quickly with no marginal cost.
Securing such 'weapons' is particularly difficult since the same people who develop and use them have the skills to exfiltrate copies without leaving traces — sometimes by using the very same 'weapons' against the organizations that contain them. 

There are substantial price incentives for government hackers and consultants to obtain copies since there is a global "vulnerability market" that will pay hundreds of thousands, or millions of dollars for copies of such 'weapons'. 
Similarly, contractors and companies who obtain such 'weapons' sometimes use them for their own purposes, obtaining advantage over their competitors in selling 'hacking' services.
Over the last three years the United States intelligence sector, which consists of government agencies such as the CIA and NSA and their contractors, such as Booze Allan Hamilton, has been subject to unprecedented series of data exfiltrations by its own workers.
A number of Intelligence Community members not yet publicly named have been arrested or subject to federal criminal investigations in separate incidents.
Uploaded 50 TB of NSA data

Most visibly, in 2017, Harold T. Martin III pled guilty to 20 counts of mishandling classified information. The Department of Justice alleged that it seized some 50,000 terabytes of information from Harold T. Martin III that he had obtained from classified programs at NSA and CIA, including the source code for numerous hacking tools. 
The US government reportedly failed to note or effectively respond to a number of issues with Martin's security practices and behaviors over a period of 10 to 20 years!
Once a single cyber 'weapon' is 'loose' it can spread around the world in seconds, to be used by peer states, cyber mafia and teenage hackers alike.


US Consulate in Frankfurt [covert CIA hacker base]

In addition to its operations in Langley, Virginia the CIA also uses the US consulate in Frankfurt as a covert base for its hackers covering Europe, the Middle East and Africa.
CIA hackers operating out of the Frankfurt consulate ( "Center for Cyber Intelligence Europe" or CCIE) are given diplomatic ("black") passports and State Department cover. The instructions for incoming CIA hackers make Germany's counter-intelligence efforts appear inconsequential: 
"Breeze through German Customs because you have your cover-for-action story down pat, and all they did was stamp your passport"
Your Cover Story (for this trip)
Q: Why are you here?
A: Supporting technical consultations at the Consulate.
Two earlier WikiLeaks publications give further detail on CIA approaches to customs and secondary screening procedures.
Once in Frankfurt CIA hackers can travel without further border checks to the 25 European countries that are part of the Shengen open border area — including France, Italy and Switzerland.
A number of the CIA's electronic attack methods are designed for physical proximity. 

These attack methods are able to penetrate high security networks that are disconnected from the internet, such as police record database. In these cases, a CIA officer, agent or allied intelligence officer acting under instructions, physically infiltrates the targeted workplace. The attacker is provided with a USB containing malware developed for the CIA for this purpose, which is inserted into the targeted computer. The attacker then infects and exfiltrates data to removable media. 
[ED Note:  Some of you may recall that this CIA team was arrested and shipped to Gitmo for trial after being monitored manipulating the 2020 election results.  They are currently enjoying the Cuban sunshine from their cells.]

For example, the CIA attack system Fine Dining, provides 24 decoy applications for CIA spies to use. To witnesses, the spy appears to be running a program showing videos (e.g VLC), presenting slides (Prezi), playing a computer game (Breakout2, 2048) or even running a fake virus scanner (Kaspersky, McAfee, Sophos). But while the decoy application is on the screen, the underlaying system is automatically infected and ransacked.

CIA increased proliferation risks

In what is surely one of the most astounding intelligence goals in living memory, the CIA structured its classification regime such that for the most market valuable part of "Vault 7" — the CIA's weaponized malware (implants + zero days), Listening Posts (LP), and Command and Control (C2) systems — the agency has little legal recourse.
The CIA made these systems unclassified.
Why the CIA chose to make its cyberarsenal unclassified reveals how concepts developed for military use do not easily crossover to the 'battlefield' of cyber 'war'.
To attack its targets, the CIA usually requires that its implants communicate with their control programs over the internet. If CIA implants, Command & Control and Listening Post software were classified, then CIA officers could be prosecuted or dismissed for violating rules that prohibit placing classified information onto the Internet. 

Consequently the CIA has secretly made most of its cyber spying/war code unclassified. 
The US government is not able to assert copyright either, due to restrictions in the US Constitution. Thus, cyber 'arms' manufactures and computer hackers can freely "pirate" these 'weapons' if they are obtained. The CIA has primarily had to rely on obfuscation to protect its malware secrets.
Conventional weapons such as missiles may be fired at the enemy (i.e., into an unsecured area). Proximity to or impact with the target detonates the ordnance including its classified parts. Hence military personnel do not violate classification rules by firing ordnance with classified parts. Ordnance will likely explode. If it does not, that is not the operator's intent [thus evidence of US involvement is available to investigators.]
Over the last decade US hacking operations have been increasingly dressed up in military jargon to tap into Department of Defense funding streams. For instance, attempted "malware injections" (commercial jargon) or "implant drops" (NSA jargon) are being called "fires" as if a weapon was being fired. However the analogy is questionable.
Unlike bullets, bombs or missiles, most CIA malware is designed to live for days or even years after it has reached its 'target'. CIA malware does not "explode on impact" but rather permanently infests its target. In order to infect target's device, copies of the malware must be placed on the target's devices, giving physical possession of the malware to the target

To exfiltrate data back to the CIA or to await further instructions the malware must communicate with CIA Command & Control (C2) systems placed on internet connected servers. But such servers are typically not approved to hold classified information, so CIA command and control systems are also made unclassified.
A successful 'attack' on a target's computer system is more like a series of complex stock maneuvers in a hostile take-over bid or the careful planting of rumors in order to gain control over an organization's leadership rather than the firing of a weapons system. 
If there is a military analogy to be made, the infestation of a target is perhaps akin to the execution of a whole series of military maneuvers against the target's territory including observation, infiltration, occupation and exploitation.

Evading Forensics and Anti-virus

A series of standards lay out CIA malware infestation patterns which are likely to assist forensic crime scene investigators as well as Apple, Microsoft, Google, Samsung, Nokia, Blackberry, Siemens and anti-virus companies attribute and defend against attacks.
"Tradecraft DO's and DON'Ts" contains CIA rules on how its malware should be written to avoid fingerprints implicating the "CIA, US government, or its witting partner companies" in "forensic review". 

Similar secret standards cover the use of encryption to hide CIA hacker and malware communication (pdf), describing targets & exfiltrated data (pdf) as well as executing payloads and persisting in the target's machines over time.
CIA hackers developed successful attacks against most well known anti-virus programs. These are documented in AV defeatsPersonal Security ProductsDetecting and Defeating PSPs and PSP/Debugger/RE Avoidance
For example, Comodo was defeated by CIA malware placing itself in the Window's "Recycle Bin". While Comodo 6.x has a "Gaping Hole of DOOM".

Examples:


The CIA's Engineering Development Group (EDG) management system contains around 500 different projects (only some of which are documented by "Year Zero"), each with their own sub-projects, malware and hacker tools.
The majority of these projects relate to tools that are used for penetration, infestation ("implanting"), control, and exfiltration.
Another branch of development focuses on the development and operation of Listening Posts (LP) and Command and Control (C2) systems used to communicate with and control CIA implants; special projects are used to target specific hardware from routers to smart TVs.
Some example projects are described below, but see the table of contents for the full list of projects described by WikiLeaks' "Year Zero".

UMBRAGE

The CIA's hand-crafted hacking techniques pose a problem for the CIA. 
Each technique it created formed a "fingerprint" that can be used by forensic investigators to attribute multiple different attacks to the same entity.
This is analogous to finding the same distinctive knife wound on multiple separate murder victims. The unique wounding style creates suspicion that a single murderer is responsible. As soon as one murder in the set is solved then the other murders will also find likely attribution.  
The CIA's Remote Devices Branch's UMBRAGE group collects and maintains a substantial library of attack techniques 'stolen' from malware produced in other states including the Russian Federation.
With UMBRAGE and related projects the CIA cannot only increase its total number of attack types but also misdirect attribution by leaving behind the "fingerprints" of the groups that the attack techniques were stolen from.
UMBRAGE components cover keyloggers, password collection, webcam capture, data destruction, persistence, privilege escalation, stealth, anti-virus (PSP) avoidance and survey techniques.

Fine Dining

Fine Dining comes with a standardized questionnaire i.e., menu that CIA case officers fill out. The questionnaire is used by the agency's OSB (Operational Support Branch) to transform the requests of case officers into technical requirements for hacking attacks (typically "exfiltrating" information from computer systems) for specific operations. The questionnaire allows the OSB to identify how to adapt existing tools for the operation, and communicate this to CIA malware configuration staff. The OSB functions as the interface between CIA operational staff and the relevant technical support staff.
Among the list of possible targets of the collection are 'Asset', 'Liason Asset', 'System Administrator', 'Foreign Information Operations', 'Foreign Intelligence Agencies' and 'Foreign Government Entities'.      
          Notably absent is any reference to extremists or transnational criminals
[As an aside, CIA can designate you as an Extremist or a Transnational Criminal]

The 'Case Officer' is also asked to specify the environment of the target like the type of computer, operating system used, Internet connectivity and installed anti-virus utilities (PSPs) as well as a list of file types to be exfiltrated like Office documents, audio, video, images or custom file types. The 'menu' also asks for information if recurring access to the target is possible and how long unobserved access to the computer can be maintained. This information is used by the CIA's 'JQJIMPROVISE' software (see below) to configure a set of CIA malware suited to the specific needs of an operation.


IMPROVISE

'Improvise' is a toolset for configuration, post-processing, payload setup and execution vector selection for survey/exfiltration tools supporting all major operating systems like Windows (Bartender), MacOS (JukeBox) and Linux (DanceFloor). Its configuration utilities like Margarita allows the NOC (Network Operation Center) to customize tools based on requirements from 'Fine Dining' questionairies.

HIVE

Hive solves critical problems for CIA malware operators
HIVE
is a multi-platform CIA malware suite and its associated control software. The project provides customizable implants for Windows, Solaris, MikroTik (used in internet routers) and Linux platforms and a Listening Post (LP)/Command and Control (C2) infrastructure to communicate with these implants.



The implants are configured to communicate via HTTPS with the web-server of a cover domain; each operation employing these implants has a separate cover domain and the infrastructure can handle any number of cover domains.
Each cover domain resolves to an IP address that is located at a commercial VPS (Virtual Private Server) provider. The public-facing server forwards all incoming traffic via a VPN to a 'Blot' server that handles actual connection requests from clients. It is set up for optional SSL client authentication: if a client sends a valid client certificate (only implants can do that), the connection is forwarded to the 'Honeycomb' tool-server that communicates with the implant; if a valid certificate is missing (which is the case if someone tries to open the cover domain website by accident), the traffic is forwarded to a cover server that delivers an unsuspicious looking website.

The Honeycomb toolserver receives exfiltrated information from the implant; an operator can also task the implant to execute jobs on the target computer, so the toolserver acts as a C2 (command and control) server for the implant.
Similar functionality (though limited to Windows) is provided by the RickBobby project.
See the classified user and developer guides for HIVE.

                      -----

Frequently Asked Questions


Why now?

WikiLeaks published as soon as its verification and analysis were ready.
In February the Trump administration  issued Executive Order 13800 calling for "Strengthening the Cybersecurity of federal networks and critical infrastructure". 

Redactions

Names, email addresses and external IP addresses were redacted in the released pages (there were 70,875 redactions in total).
  1. Over-redaction: Some items may have been redacted that are not employees, contractors, targets or otherwise related to the agency, but are, for example, authors of documentation for otherwise public projects that are used by the agency.
  2. Identity vs. person: the redacted names are replaced by user IDs (numbers) to allow readers to assign multiple pages to a single author. Given the redaction process used a single person may be represented by more than one assigned identifier but no identifier refers to more than one real person.
  3. Archive attachments (zip, tar.gz, ...) are replaced with a PDF listing all the file names in the archive. As the archive content is assessed it may be made available; until then the archive is redacted.
  4. Attachments with other binary content are replaced by a hex dump of the content to prevent accidental invocation of binaries that may have been infected with weaponized CIA malware. As the content is assessed it may be made available; until then the content is redacted.
  5. The tens of thousands of routable IP addresses references (including more than 22 thousand within the United States) that correspond to possible targets, CIA covert listening post servers, intermediary and test systems, are redacted for further exclusive investigation.
  6. Binary files of non-public origin are only available as dumps to prevent accidental invocation of CIA malware infected binaries.

Organizational Chart

The organizational chart corresponds to the material published by WikiLeaks.
Since the organizational structure of the CIA below the level of Directorates is not public, the placement of the EDG and its branches within the org chart of the agency is reconstructed from information contained in the documents released so far. It is intended to be used as a rough outline of the internal organization; the reconstructed organization chart is incomplete and that internal reorganizations occur frequently.

Wiki pages

"Year Zero" contains 78,18 web pages with 943 attachments from the internal development groupware. The software used for this purpose is called Confluence, a proprietary software from Atlassian. Webpages in this system (as in Wikipedia) have a version history that can provide interesting insights on how a document evolved over time; the 7,818 documents included these page histories for 1,136 latest versions.
The order of named pages within each level is determined by date (oldest first). Page content is not present if it was originally dynamically created by the Confluence software (as indicated on the re-constructed page).

What time period is covered?

The years 2013 to 2016. The sort order of the pages within each level is determined by date (oldest first).
WikiLeaks obtained the CIA's creation/last modification date for each page but these don'tt appear for technical reasons. Usually the date can be discerned or approximated from the content and the page order. If it is critical to know the exact time/date contact WikiLeaks.

What is "Vault 7"

"Vault 7" is a substantial collection of material about CIA activities obtained by WikiLeaks.

When was each part of "Vault 7" obtained?
Part one was obtained recently and covers through 2016. Details on the other parts will be available at the time of publication.

Is each part of "Vault 7" from a different source?

Details on parts will be available at the time of publication.

What is the total size of "Vault 7"?

The series is the largest intelligence publication in history.

Isn't WikiLeaks worried that the CIA will act against its staff to stop the series?

No. That would be certainly counter-productive.

Has WikiLeaks already 'mined' all the best stories?

No. WikiLeaks has intentionally not written up hundreds of impactful stories to encourage others to find them and so create expertise in the area for subsequent parts in the series. They exist; search for them.