KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#ai
#dsh-plugin
#deepseek-harness
#open-source
#cli
#claude-code
#codex
#developer-tools
#react
#windows
crux
★ 96
Open GitHub ↗
A proof-of-concept malicious Chrome extension
Download README (.md)
Explore Similar Repositories
hivemq-mqtt-client-dotnet
:
Spectacular C# MQTT and Sparkplug Clients for .NET
Tidme
:
Tidme uses advanced Incremental Learning concepts to make it your powerful second brain for acquiring lifelong knowledge.
huggingface-inference-toolkit
:
Hugging Face Inference Toolkit used to serve transformers, sentence-transformers, and diffusers models.
Dorisoy.POS
:
使用.Net7 + Angular4开发的一套新零售快消进销存管理系统，带库存管理的高级轻量级POS，具有闪电般的性能和开箱即用的页面加载速度。
URP-Render-Features
:
Custom render features for URP using RenderGraph. Includes outlines, desaturation and blur.
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
crux
?
Download (.md)
# Crux: Demonstration Malicious Chrome Extension This repository is for **educational purposes only**. If you use this outside of security research or authorized pentests, you're doing crimes. Don't do crimes. ## Objective This tool is intended to demonstrate the risk posed by malicious Chrome extensions, and how they can be loaded into users' browsers to disclose secrets. The extension is designed to report cookies, URLs, and form data to a listening server. The result is an extension that can move an unprivileged RCE to credentialed elevation and other kinds of pivoting. ## Usage The repository contains 2 directories: `extension` and `server`. Let's begin with the server. ### Server Clone this repository to any server accessible from your victim. Make sure Flask and Rich are installed with `pip3 install flask rich`. Then, simply run `flask run [port]`. Your server is now listening for data. ### Extension Before launching the extension on the victim server, make sure to change the `server_host` variable in `background.js` to match your listening server. ### Deployment This is a post-compromise tool. With the delivery option of your choice, upload the extension folder to a location on the target system. For proper OPSEC, I recommend the appropriate folder for extensions for the given browser. Once the unpacked extension has been deployed, launch the desired Chromium-based browser with `/path/to/browser --load-extension='C:/path/to/extension`. You can use other command-line options as desired, or even follow the [ChromeLoader](https://unit42.paloaltonetworks.com/chromeloader-malware/) playbook:  Once the browser is open and communicating with the server, all you have to do is wait for data to come in.
