Replies

You likely have seen this.

Kraken is a US Counter Intelligence dynamic cyber AI program, which was/is designed to sniff out near traceless algorithms and fractals, global anonymous intrusions, and to define them. It is reportedly especially capable in tracking the SCYTL related voting cloud umbrella, and may have been created or adapted after Trump’s 2017/2018 EO’s related to cyber security, and elections security.

One description —

WikiLeaks

Vault 7: CIA Hacking Tools Revealed

Releases Documents

Navigation: » Directory » Kraken » kraken Home

Owner: User #20251227
Project Overview
Current Status
Current Activities: go look at the current sprint in JIRA

Useful Pointers

Stash: https://stash.devlan.net/projects/KRAK

Jira: https://jira.ioc.local/projects/KRAK/summary

Components/Architecture

Client - The component that resides on a target and does things. Communicates with a (paired) Listener.

Listener - The component that communicates with multiple (paired) Clients and the Manager. The Listener functions mainly as a “translator” for messages/commands between the Manager and a given client.

Manager - The component that communicates with the Listener, User Interface (UI), and data store(s) (e.g., database). The Manager is responsible for noting the commands of a user and tasking/managing collections of clients via associated Listeners so that a user can achieve desired goals.

User Interface (UI) - A Command Line Interface (CLI) via which a user describes the actions that clients should take and, additionally, what data (historical & current) should be displayed.

Conventions

a) All code comments, etc are Doxygen style, and Doxygen will be used to generate developer docs. This is for both the Python & native components.

b) Ideally, there should be dev/build VM image(s) under config management of some sort and the details on how they were built/modified so that they can be reproduced.

c) Git & Stash for version control

“Feature Branch”-based workflowuse the “—no-ff” (no ‘fast-forward’ switch), always.... this helps keep explicit branch history. references here: a successful git branching model,

stackoverflow.com/questions/9069061/what-is-the-difference-between-git-merge-and-git-merge-no-ffBEWARE: Git wants to do “ff” style merges...when PULLing, etc. Git is sneaky and will do what Git wants unless you keep an eye on Git, like, a “one-eye-open-while-sleeping”