☠️ NullSec DataPoisoning
Training Data Poisoning Detection & Simulation
Detect, simulate, and defend against training data poisoning attacks
🎯 Overview
NullSec DataPoisoning provides tools for detecting and simulating data poisoning attacks against machine learning pipelines. It implements backdoor injection (BadNets, Trojaning), clean-label attacks, and gradient-based poisoning, alongside detection methods like spectral signatures, activation clustering, and STRIP.
⚡ Features
| Feature | Description |
|---|---|
| Backdoor Injection | BadNets, Trojan, blend, and warp triggers |
| Clean-Label Attacks | Feature collision, convex polytope, Witches' Brew |
| Detection Engine | Spectral signatures, activation clustering, STRIP |
| Neural Cleanse | Reverse-engineer trigger patterns from poisoned models |
| Dataset Audit | Scan datasets for anomalous samples and label flips |
| Pipeline Scanner | Audit ML pipelines for poisoning entry points |
📋 Attack & Defence Matrix
| Technique | Category | Type |
|---|---|---|
| BadNets | Backdoor | Attack |
| Trojan Attack | Backdoor | Attack |
| Clean-Label FC | Poisoning | Attack |
| Witches' Brew | Poisoning | Attack |
| Spectral Signatures | Statistical | Defence |
| Activation Clustering | Neural | Defence |
| STRIP | Runtime | Defence |
| Neural Cleanse | Reverse Engineering | Defence |
🚀 Quick Start
# Scan a dataset for poisoning indicators
nullsec-datapoisoning scan --dataset training_data/ --model model.pt
# Simulate backdoor attack
nullsec-datapoisoning inject --dataset clean.csv --trigger patch --target-label 0 --poison-rate 0.01
# Run Neural Cleanse detection
nullsec-datapoisoning cleanse --model suspect_model.pt --num-classes 10
# Audit an ML pipeline config
nullsec-datapoisoning audit --pipeline pipeline.yaml
🔗 Related Projects
| Project | Description |
|---|---|
| nullsec-adversarial | Adversarial ML attack toolkit |
| nullsec-modelaudit | ML model security auditing |
| nullsec-llmred | LLM red-teaming framework |
| nullsec-promptinject | Prompt injection payloads |
| nullsec-linux | Security Linux distro (140+ tools) |
⚠️ Legal
For authorized ML security research only. Poisoning production training data without authorization is illegal.
📜 License
MIT License — @bad-antics
Part of the NullSec AI/ML Security Suite
Metadata
Release files for nullsec-datapoisoning 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nullsec_datapoisoning-0.1.0.tar.gz | 10.0 kB | Without provenance | Details for nullsec_datapoisoning-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nullsec_datapoisoning-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for nullsec_datapoisoning-0.1.0-py3-none-any.whl |
Total release size: 20.2 kB
Release files / nullsec_datapoisoning-0.1.0.tar.gz
| Download URL | nullsec_datapoisoning-0.1.0.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94f12895d1fddfd7b43c6d695a3bb6558771c439de238d2f4805becae01ff669
|
|
BLAKE2b-256 checksum How to use checksums |
baa6cac269eefc5d121aad4ecae206f6a39ad67478fcafb4e55c3397648f1c89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / nullsec_datapoisoning-0.1.0-py3-none-any.whl
| Download URL | nullsec_datapoisoning-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b3b2085816617d286acdf55b7bfa09b3470f451784cf124235b51e64a597954
|
|
BLAKE2b-256 checksum How to use checksums |
484026db6a43c53b011be4ee9878caaf16da0ec277335df6f40d86a7733a434a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for nullsec-datapoisoning 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.