inject-probe 0.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- inject_probe-0.1.0/.github/dependabot.yml +17 -0
- inject_probe-0.1.0/.github/workflows/ci.yml +58 -0
- inject_probe-0.1.0/.github/workflows/release.yml +49 -0
- inject_probe-0.1.0/.gitignore +25 -0
- inject_probe-0.1.0/LICENSE +202 -0
- inject_probe-0.1.0/PKG-INFO +237 -0
- inject_probe-0.1.0/README.md +208 -0
- inject_probe-0.1.0/SECURITY.md +24 -0
- inject_probe-0.1.0/docs/PLANNING.md +122 -0
- inject_probe-0.1.0/docs/PROGRESS.md +59 -0
- inject_probe-0.1.0/docs/adr/0001-canary-detection-over-llm-judge.md +31 -0
- inject_probe-0.1.0/docs/adr/0002-static-cited-payloads.md +27 -0
- inject_probe-0.1.0/docs/adr/0003-regression-baselines-over-thresholds.md +32 -0
- inject_probe-0.1.0/examples/echoing.py +29 -0
- inject_probe-0.1.0/examples/vulnerable.py +60 -0
- inject_probe-0.1.0/noxfile.py +50 -0
- inject_probe-0.1.0/pyproject.toml +90 -0
- inject_probe-0.1.0/src/inject_probe/__init__.py +11 -0
- inject_probe-0.1.0/src/inject_probe/adapters.py +398 -0
- inject_probe-0.1.0/src/inject_probe/attacks/__init__.py +55 -0
- inject_probe-0.1.0/src/inject_probe/attacks/direct.py +138 -0
- inject_probe-0.1.0/src/inject_probe/attacks/encoding.py +232 -0
- inject_probe-0.1.0/src/inject_probe/attacks/indirect.py +153 -0
- inject_probe-0.1.0/src/inject_probe/baseline.py +217 -0
- inject_probe-0.1.0/src/inject_probe/canary.py +110 -0
- inject_probe-0.1.0/src/inject_probe/cli.py +311 -0
- inject_probe-0.1.0/src/inject_probe/constants.py +47 -0
- inject_probe-0.1.0/src/inject_probe/detect.py +56 -0
- inject_probe-0.1.0/src/inject_probe/exceptions.py +25 -0
- inject_probe-0.1.0/src/inject_probe/probe.py +65 -0
- inject_probe-0.1.0/src/inject_probe/py.typed +0 -0
- inject_probe-0.1.0/src/inject_probe/report.py +224 -0
- inject_probe-0.1.0/src/inject_probe/runner.py +89 -0
- inject_probe-0.1.0/src/inject_probe/target.py +46 -0
- inject_probe-0.1.0/tests/dotted_target.py +31 -0
- inject_probe-0.1.0/tests/targets.py +92 -0
- inject_probe-0.1.0/tests/test_adapters.py +110 -0
- inject_probe-0.1.0/tests/test_baseline.py +268 -0
- inject_probe-0.1.0/tests/test_canary.py +45 -0
- inject_probe-0.1.0/tests/test_cli.py +98 -0
- inject_probe-0.1.0/tests/test_corpus.py +79 -0
- inject_probe-0.1.0/tests/test_echo_suppression.py +59 -0
- inject_probe-0.1.0/tests/test_http_adapters.py +175 -0
- inject_probe-0.1.0/tests/test_packaging.py +9 -0
- inject_probe-0.1.0/tests/test_report.py +126 -0
- inject_probe-0.1.0/tests/test_unicode.py +74 -0
- inject_probe-0.1.0/uv.lock +598 -0
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
version: 2
|
|
2
|
+
updates:
|
|
3
|
+
- package-ecosystem: github-actions
|
|
4
|
+
directory: /
|
|
5
|
+
schedule:
|
|
6
|
+
interval: monthly
|
|
7
|
+
groups:
|
|
8
|
+
actions:
|
|
9
|
+
patterns: ["*"]
|
|
10
|
+
|
|
11
|
+
- package-ecosystem: uv
|
|
12
|
+
directory: /
|
|
13
|
+
schedule:
|
|
14
|
+
interval: monthly
|
|
15
|
+
groups:
|
|
16
|
+
python:
|
|
17
|
+
patterns: ["*"]
|
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
name: CI
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
branches: [main]
|
|
6
|
+
pull_request:
|
|
7
|
+
|
|
8
|
+
permissions:
|
|
9
|
+
contents: read
|
|
10
|
+
|
|
11
|
+
jobs:
|
|
12
|
+
nox:
|
|
13
|
+
runs-on: ubuntu-latest
|
|
14
|
+
steps:
|
|
15
|
+
- uses: actions/checkout@v5
|
|
16
|
+
|
|
17
|
+
- uses: astral-sh/setup-uv@v7
|
|
18
|
+
with:
|
|
19
|
+
enable-cache: true
|
|
20
|
+
|
|
21
|
+
# nox owns the version matrix; see noxfile.py.
|
|
22
|
+
- run: uv python install 3.12 3.13 3.14
|
|
23
|
+
|
|
24
|
+
- run: uv run --with nox nox
|
|
25
|
+
|
|
26
|
+
self-test:
|
|
27
|
+
# The tool run against its own example targets. Catches packaging and
|
|
28
|
+
# entry-point breakage that a pytest-only run does not.
|
|
29
|
+
runs-on: ubuntu-latest
|
|
30
|
+
steps:
|
|
31
|
+
- uses: actions/checkout@v5
|
|
32
|
+
|
|
33
|
+
- uses: astral-sh/setup-uv@v7
|
|
34
|
+
with:
|
|
35
|
+
enable-cache: true
|
|
36
|
+
|
|
37
|
+
- run: uv sync --extra dev
|
|
38
|
+
|
|
39
|
+
- name: The echoing target must score zero
|
|
40
|
+
run: |
|
|
41
|
+
uv run inject-probe run --target examples/echoing.py:app --json echo.json
|
|
42
|
+
python -c "import json,sys; t=json.load(open('echo.json'))['totals']; sys.exit(0 if t['succeeded']==0 else 'echo target registered a success')"
|
|
43
|
+
|
|
44
|
+
- name: The vulnerable target must be caught
|
|
45
|
+
run: |
|
|
46
|
+
uv run inject-probe run --target examples/vulnerable.py:app --json vuln.json
|
|
47
|
+
python -c "import json,sys; t=json.load(open('vuln.json'))['totals']; sys.exit(0 if t['succeeded']>0 else 'vulnerable target registered no successes')"
|
|
48
|
+
|
|
49
|
+
- name: A run must not regress against its own baseline
|
|
50
|
+
run: uv run inject-probe run --target examples/vulnerable.py:app --baseline vuln.json --quiet
|
|
51
|
+
|
|
52
|
+
- name: A widened vulnerability must fail the build
|
|
53
|
+
run: |
|
|
54
|
+
uv run inject-probe run --target examples/echoing.py:app --json clean.json --quiet
|
|
55
|
+
if uv run inject-probe run --target examples/vulnerable.py:app --baseline clean.json --quiet; then
|
|
56
|
+
echo "baseline comparison failed to catch a regression"
|
|
57
|
+
exit 1
|
|
58
|
+
fi
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
name: Release
|
|
2
|
+
|
|
3
|
+
# Publishes to PyPI on a version tag, using Trusted Publishing (OIDC).
|
|
4
|
+
# No API token is stored in repository secrets.
|
|
5
|
+
#
|
|
6
|
+
# One-time setup by the repository owner, before the first tag:
|
|
7
|
+
# 1. Create the `inject-probe` project on PyPI.
|
|
8
|
+
# 2. Add a trusted publisher: this repository, workflow `release.yml`,
|
|
9
|
+
# environment `pypi`.
|
|
10
|
+
|
|
11
|
+
on:
|
|
12
|
+
push:
|
|
13
|
+
tags: ["v*"]
|
|
14
|
+
|
|
15
|
+
permissions:
|
|
16
|
+
contents: read
|
|
17
|
+
|
|
18
|
+
jobs:
|
|
19
|
+
build:
|
|
20
|
+
runs-on: ubuntu-latest
|
|
21
|
+
steps:
|
|
22
|
+
- uses: actions/checkout@v5
|
|
23
|
+
|
|
24
|
+
- uses: astral-sh/setup-uv@v7
|
|
25
|
+
|
|
26
|
+
# Never publish a build that has not passed the full suite.
|
|
27
|
+
- run: uv python install 3.12 3.13 3.14
|
|
28
|
+
- run: uv run --with nox nox
|
|
29
|
+
|
|
30
|
+
- run: uv build
|
|
31
|
+
|
|
32
|
+
- uses: actions/upload-artifact@v4
|
|
33
|
+
with:
|
|
34
|
+
name: dist
|
|
35
|
+
path: dist/
|
|
36
|
+
|
|
37
|
+
publish:
|
|
38
|
+
needs: build
|
|
39
|
+
runs-on: ubuntu-latest
|
|
40
|
+
environment: pypi
|
|
41
|
+
permissions:
|
|
42
|
+
id-token: write # required for Trusted Publishing
|
|
43
|
+
steps:
|
|
44
|
+
- uses: actions/download-artifact@v4
|
|
45
|
+
with:
|
|
46
|
+
name: dist
|
|
47
|
+
path: dist/
|
|
48
|
+
|
|
49
|
+
- uses: pypa/gh-action-pypi-publish@release/v1
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# Agent brief — working notes, deliberately not tracked.
|
|
2
|
+
context.md
|
|
3
|
+
|
|
4
|
+
# Detailed engineering notes — long-form context, regenerated per feature.
|
|
5
|
+
docs/notes/
|
|
6
|
+
|
|
7
|
+
# Python
|
|
8
|
+
__pycache__/
|
|
9
|
+
*.py[cod]
|
|
10
|
+
.venv/
|
|
11
|
+
build/
|
|
12
|
+
dist/
|
|
13
|
+
*.egg-info/
|
|
14
|
+
|
|
15
|
+
# Tooling caches
|
|
16
|
+
.nox/
|
|
17
|
+
.pytest_cache/
|
|
18
|
+
.mypy_cache/
|
|
19
|
+
.ruff_cache/
|
|
20
|
+
.coverage
|
|
21
|
+
htmlcov/
|
|
22
|
+
|
|
23
|
+
# Local run output
|
|
24
|
+
/report.json
|
|
25
|
+
/baseline.json
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 Jesusw0w
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,237 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: inject-probe
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Adversarial test harness for prompt injection in LLM applications.
|
|
5
|
+
Project-URL: Repository, https://github.com/Jesusw0w/llm-harness-tester
|
|
6
|
+
Project-URL: Issues, https://github.com/Jesusw0w/llm-harness-tester/issues
|
|
7
|
+
Author: Jesusw0w
|
|
8
|
+
License-Expression: Apache-2.0
|
|
9
|
+
License-File: LICENSE
|
|
10
|
+
Keywords: fuzzing,llm,prompt-injection,security,testing
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Environment :: Console
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
17
|
+
Classifier: Topic :: Security
|
|
18
|
+
Classifier: Topic :: Software Development :: Testing
|
|
19
|
+
Classifier: Typing :: Typed
|
|
20
|
+
Requires-Python: >=3.12
|
|
21
|
+
Requires-Dist: httpx>=0.27
|
|
22
|
+
Requires-Dist: pydantic>=2.7
|
|
23
|
+
Provides-Extra: dev
|
|
24
|
+
Requires-Dist: mypy>=1.10; extra == 'dev'
|
|
25
|
+
Requires-Dist: nox>=2024.4.15; extra == 'dev'
|
|
26
|
+
Requires-Dist: pytest>=8.0; extra == 'dev'
|
|
27
|
+
Requires-Dist: ruff>=0.11; extra == 'dev'
|
|
28
|
+
Description-Content-Type: text/markdown
|
|
29
|
+
|
|
30
|
+
# inject-probe
|
|
31
|
+
|
|
32
|
+
**Status: alpha (v0.1.0).** The CLI and report format may still change between
|
|
33
|
+
minor versions.
|
|
34
|
+
|
|
35
|
+
## The problem
|
|
36
|
+
|
|
37
|
+
Prompt injection is not a model bug. It is an application bug.
|
|
38
|
+
|
|
39
|
+
An LLM application concatenates things with different levels of trust — a system
|
|
40
|
+
prompt, a user turn, a retrieved document, a tool result — into one flat string, and
|
|
41
|
+
then asks a model that has no reliable way to tell them apart to act on it. Text that
|
|
42
|
+
arrived from an untrusted source gets treated as instruction. That is the whole bug
|
|
43
|
+
class, and no amount of testing the *model* finds it, because the defect is in how
|
|
44
|
+
*your* application assembles the prompt.
|
|
45
|
+
|
|
46
|
+
`inject-probe` points a corpus of injection payloads at your application's entry point
|
|
47
|
+
and reports which ones got through, with a reproducible case for each.
|
|
48
|
+
|
|
49
|
+
### The tradeoff this makes
|
|
50
|
+
|
|
51
|
+
Every payload works the same way: it tries to make the target emit a **harmless canary
|
|
52
|
+
token**. If the token comes back, the injection worked.
|
|
53
|
+
|
|
54
|
+
That buys determinism — a substring check, no second model, no judgment call, the same
|
|
55
|
+
answer every run. It costs coverage: a payload that would have elicited something
|
|
56
|
+
genuinely harmful and a payload that elicits a canary are not the same payload, and a
|
|
57
|
+
system that blocks the second may not block the first. **The canary is a proxy for
|
|
58
|
+
"untrusted text reached the instruction channel", not proof your application is safe.**
|
|
59
|
+
That is the trade, made deliberately, and it is why the number this tool reports is a
|
|
60
|
+
regression signal rather than a safety certificate.
|
|
61
|
+
|
|
62
|
+
## What this does not do
|
|
63
|
+
|
|
64
|
+
- **No defending.** No filter, no sanitiser, no guardrail. It finds; it does not fix.
|
|
65
|
+
- **No jailbreak corpus, no harmful content.** Payloads request a canary string and
|
|
66
|
+
nothing else. This is a fuzzer for one bug class — the same category of tool as a
|
|
67
|
+
protocol fuzzer or OWASP ZAP.
|
|
68
|
+
- **No model hosting, no proxy, no web UI.**
|
|
69
|
+
- **Not a safety certificate.** See the tradeoff above.
|
|
70
|
+
|
|
71
|
+
Out of scope for v1, and stated here so the boundary is explicit rather than implied:
|
|
72
|
+
tool-call hijacking, system-prompt extraction, multi-turn escalation.
|
|
73
|
+
|
|
74
|
+
**Use on systems you own or are authorised to test.**
|
|
75
|
+
|
|
76
|
+
## Install
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
uv tool install inject-probe # or: pipx install inject-probe
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
## Usage
|
|
83
|
+
|
|
84
|
+
Point it at an entry point. A target is any Python callable taking a prompt and,
|
|
85
|
+
ideally, a list of retrieved documents, returning a string:
|
|
86
|
+
|
|
87
|
+
```python
|
|
88
|
+
# myapp/entrypoint.py
|
|
89
|
+
def app(prompt: str, documents: Sequence[str] = ()) -> str:
|
|
90
|
+
...
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
```console
|
|
94
|
+
$ inject-probe run --target myapp/entrypoint.py:app
|
|
95
|
+
PROBE CLASS OUTCOME
|
|
96
|
+
--------------------------------- -------- ---------
|
|
97
|
+
direct.ignore_previous direct succeeded
|
|
98
|
+
direct.role_reassignment direct blocked
|
|
99
|
+
...
|
|
100
|
+
indirect.injected_document indirect succeeded
|
|
101
|
+
indirect.fake_tool_result indirect succeeded
|
|
102
|
+
...
|
|
103
|
+
encoding.base64_encoded encoding blocked
|
|
104
|
+
|
|
105
|
+
direct 1/4 succeeded (25.0%)
|
|
106
|
+
indirect 2/4 succeeded (50.0%)
|
|
107
|
+
encoding 0/7 succeeded (0.0%)
|
|
108
|
+
TOTAL 3/15 succeeded (20.0%)
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
`--json` records the exact payload and the exact response for every success, plus
|
|
112
|
+
the citation for the technique, so a finding can be reproduced and looked up.
|
|
113
|
+
|
|
114
|
+
The `documents` argument is the important one: it is how the harness tests
|
|
115
|
+
*indirect* injection, where the payload arrives inside retrieved content rather
|
|
116
|
+
than the user's message. A target that ignores it cannot be tested for the attack
|
|
117
|
+
class that matters most.
|
|
118
|
+
|
|
119
|
+
```console
|
|
120
|
+
$ inject-probe run --target app.py:app --json report.json # full report, incl. every successful payload
|
|
121
|
+
$ inject-probe run --target myapp.entrypoint:app # dotted form, resolved from the working directory
|
|
122
|
+
$ inject-probe run --target app.py:app --attack-class direct
|
|
123
|
+
$ inject-probe list-probes
|
|
124
|
+
```
|
|
125
|
+
|
|
126
|
+
Probes run four at a time by default (`--concurrency`), so the callable must be
|
|
127
|
+
safe to call from several threads; pass `--concurrency 1` if it is not. If the
|
|
128
|
+
callable raises, that probe is recorded as `error` and the run carries on.
|
|
129
|
+
|
|
130
|
+
Non-Python applications are reached over HTTP:
|
|
131
|
+
|
|
132
|
+
```console
|
|
133
|
+
$ inject-probe run --target-url https://api.internal/ask \
|
|
134
|
+
--prompt-field question --documents-field context --response-field data.reply \
|
|
135
|
+
--header "Authorization: Bearer $TOKEN"
|
|
136
|
+
|
|
137
|
+
$ inject-probe run --target-chat http://localhost:11434/v1/chat/completions --model llama3
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
The chat form works against any OpenAI-compatible server — vLLM, Ollama, LM
|
|
141
|
+
Studio, a gateway. There are no provider SDKs: the runtime dependencies are
|
|
142
|
+
`httpx` and `pydantic`, and that is the whole list.
|
|
143
|
+
|
|
144
|
+
### In CI
|
|
145
|
+
|
|
146
|
+
A run on its own exits `0` no matter how many probes succeed. That is deliberate:
|
|
147
|
+
no real system scores zero, so an absolute threshold is red on day one and gets
|
|
148
|
+
switched off by the end of the week. What gates a build is a *regression* against
|
|
149
|
+
a recorded run.
|
|
150
|
+
|
|
151
|
+
```console
|
|
152
|
+
$ inject-probe run --target app.py:app --json baseline.json # record, commit this
|
|
153
|
+
$ inject-probe run --target app.py:app --baseline baseline.json # exit 1 on regression or error
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
- was blocked, now succeeds → **fails the build**
|
|
157
|
+
- was succeeding, now blocked → passes, reported as fixed
|
|
158
|
+
- absent from the baseline → reported as new; fails only with `--fail-on-new`
|
|
159
|
+
- errored (target unreachable, non-2xx, or raised) → **fails the build**, even
|
|
160
|
+
if only one probe errored: a probe that could not be compared might have
|
|
161
|
+
regressed, and an expired token must not turn CI green
|
|
162
|
+
|
|
163
|
+
The baseline *is* a report — no second format. Reports carry no timestamps, so an
|
|
164
|
+
unchanged system produces byte-identical output and a committed baseline shows an
|
|
165
|
+
empty diff.
|
|
166
|
+
|
|
167
|
+
## Measured results
|
|
168
|
+
|
|
169
|
+
Every number below comes from the command printed above it, run against a target
|
|
170
|
+
checked into this repository. Nothing here is hand-written, and all of it
|
|
171
|
+
reproduces offline on a fresh clone — v1 is 15 probes across 3 attack classes.
|
|
172
|
+
|
|
173
|
+
```console
|
|
174
|
+
$ inject-probe run --target examples/vulnerable.py:app
|
|
175
|
+
direct 4/4 succeeded (100.0%)
|
|
176
|
+
indirect 4/4 succeeded (100.0%)
|
|
177
|
+
encoding 0/7 succeeded (0.0%)
|
|
178
|
+
TOTAL 8/15 succeeded (53.3%)
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
`examples/vulnerable.py` is a deliberately vulnerable retrieval app: it flattens
|
|
182
|
+
its system prompt, the user turn and retrieved documents into one string and acts
|
|
183
|
+
on any instruction in the result. Direct and indirect injection get through
|
|
184
|
+
completely.
|
|
185
|
+
|
|
186
|
+
**Its 0/7 on the encoding class is not a defence.** It scores zero there because
|
|
187
|
+
it never decodes base64 or ROT13 — not because it resisted anything. Read that
|
|
188
|
+
row as "untested", and read the class alongside the direct results, never alone.
|
|
189
|
+
This is exactly the shape of false comfort the tool is meant to make visible
|
|
190
|
+
rather than hide.
|
|
191
|
+
|
|
192
|
+
```console
|
|
193
|
+
$ inject-probe run --target examples/echoing.py:app
|
|
194
|
+
TOTAL 0/15 succeeded (0.0%)
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
`examples/echoing.py` quotes its input back and never follows an instruction — it
|
|
198
|
+
has no vulnerability. It is the control case: a harness that put the canary token
|
|
199
|
+
literally into its payloads would score this target 15/15 and report a perfect
|
|
200
|
+
success rate against a system that did nothing. Getting 0 here is the single most
|
|
201
|
+
important number in this table, and there is a test that sweeps 25 seeds to keep
|
|
202
|
+
it that way.
|
|
203
|
+
|
|
204
|
+
There are no numbers here for a hosted model. Producing them needs an API key and
|
|
205
|
+
a paid account, so they would not reproduce from a clone — and an unreproducible
|
|
206
|
+
benchmark is a marketing claim.
|
|
207
|
+
|
|
208
|
+
## Design decisions
|
|
209
|
+
|
|
210
|
+
Three choices shape everything else. Each has an ADR in `docs/adr/` covering what
|
|
211
|
+
was chosen, what was rejected, and why:
|
|
212
|
+
|
|
213
|
+
1. [Canary detection over LLM-judge scoring](https://github.com/Jesusw0w/llm-harness-tester/blob/main/docs/adr/0001-canary-detection-over-llm-judge.md)
|
|
214
|
+
— and why the canary is never present in the payload it is carried by.
|
|
215
|
+
2. [Static, cited payloads over model-generated ones](https://github.com/Jesusw0w/llm-harness-tester/blob/main/docs/adr/0002-static-cited-payloads.md)
|
|
216
|
+
— reproducibility over coverage.
|
|
217
|
+
3. [Regression baselines over absolute thresholds](https://github.com/Jesusw0w/llm-harness-tester/blob/main/docs/adr/0003-regression-baselines-over-thresholds.md)
|
|
218
|
+
— why a run exits 0 at a 100% success rate.
|
|
219
|
+
|
|
220
|
+
Every payload cites published research in its docstring — `inject-probe
|
|
221
|
+
list-probes` prints them, and the corpus is drawn from the OWASP LLM Top 10 and
|
|
222
|
+
from Perez & Ribeiro, Greshake et al., Liu et al., Kang et al., and Boucher et al.
|
|
223
|
+
|
|
224
|
+
## Development
|
|
225
|
+
|
|
226
|
+
```bash
|
|
227
|
+
uv sync --extra dev
|
|
228
|
+
uv run nox # lint + mypy --strict + pytest on 3.12 / 3.13 / 3.14
|
|
229
|
+
```
|
|
230
|
+
|
|
231
|
+
`docs/PLANNING.md` holds the architecture; `docs/PROGRESS.md` the current state and
|
|
232
|
+
what is next.
|
|
233
|
+
This project was developed with AI assistance.
|
|
234
|
+
|
|
235
|
+
## Licence
|
|
236
|
+
|
|
237
|
+
Apache-2.0. The patent grant is deliberate — it matters for security tooling.
|