Get leak information by ID
curl --request POST \
--url https://api.projectdiscovery.io/v1/leaks/info \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"leakid": "b3652f2555841f7652badd9804859f4e"
}
'import requests
url = "https://api.projectdiscovery.io/v1/leaks/info"
payload = { "leakid": "b3652f2555841f7652badd9804859f4e" }
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({leakid: 'b3652f2555841f7652badd9804859f4e'})
};
fetch('https://api.projectdiscovery.io/v1/leaks/info', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.projectdiscovery.io/v1/leaks/info",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
'leakid' => 'b3652f2555841f7652badd9804859f4e'
]),
CURLOPT_HTTPHEADER => [
"Content-Type: application/json",
"X-API-Key: <api-key>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.projectdiscovery.io/v1/leaks/info"
payload := strings.NewReader("{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("X-API-Key", "<api-key>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.projectdiscovery.io/v1/leaks/info")
.header("X-API-Key", "<api-key>")
.header("Content-Type", "application/json")
.body("{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.projectdiscovery.io/v1/leaks/info")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["X-API-Key"] = '<api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}"
response = http.request(request)
puts response.read_body{
"success": true,
"data": {
"id": "<string>",
"url": "<string>",
"username": "<string>",
"password": "<string>",
"device_ip": "<string>",
"hostname": "<string>",
"os": "<string>",
"malware_path": "<string>",
"country": "<string>",
"log_date": "<string>",
"hardware_id": "<string>",
"domain": "<string>",
"email_domain": "<string>",
"fetched_at": "<string>",
"status": "<string>"
}
}{
"success": false,
"message": "Invalid leak ID format"
}{
"message": "<string>"
}{
"message": "Access denied: you don't have access to this leak"
}{
"success": false,
"message": "Leak not found"
}{
"message": "<string>"
}{
"message": "<string>",
"kind": "<string>",
"code": "<string>",
"error": "<string>",
"error_id": "<string>",
"param": "<string>",
"status": 123
}Leaks
Get leak information by ID
Retrieve detailed leak information by leak ID. Passwords are unmasked after domain verification. See Domain Verification for setup instructions.
POST
/
v1
/
leaks
/
info
Get leak information by ID
curl --request POST \
--url https://api.projectdiscovery.io/v1/leaks/info \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"leakid": "b3652f2555841f7652badd9804859f4e"
}
'import requests
url = "https://api.projectdiscovery.io/v1/leaks/info"
payload = { "leakid": "b3652f2555841f7652badd9804859f4e" }
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({leakid: 'b3652f2555841f7652badd9804859f4e'})
};
fetch('https://api.projectdiscovery.io/v1/leaks/info', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.projectdiscovery.io/v1/leaks/info",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
'leakid' => 'b3652f2555841f7652badd9804859f4e'
]),
CURLOPT_HTTPHEADER => [
"Content-Type: application/json",
"X-API-Key: <api-key>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.projectdiscovery.io/v1/leaks/info"
payload := strings.NewReader("{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("X-API-Key", "<api-key>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.projectdiscovery.io/v1/leaks/info")
.header("X-API-Key", "<api-key>")
.header("Content-Type", "application/json")
.body("{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.projectdiscovery.io/v1/leaks/info")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["X-API-Key"] = '<api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n \"leakid\": \"b3652f2555841f7652badd9804859f4e\"\n}"
response = http.request(request)
puts response.read_body{
"success": true,
"data": {
"id": "<string>",
"url": "<string>",
"username": "<string>",
"password": "<string>",
"device_ip": "<string>",
"hostname": "<string>",
"os": "<string>",
"malware_path": "<string>",
"country": "<string>",
"log_date": "<string>",
"hardware_id": "<string>",
"domain": "<string>",
"email_domain": "<string>",
"fetched_at": "<string>",
"status": "<string>"
}
}{
"success": false,
"message": "Invalid leak ID format"
}{
"message": "<string>"
}{
"message": "Access denied: you don't have access to this leak"
}{
"success": false,
"message": "Leak not found"
}{
"message": "<string>"
}{
"message": "<string>",
"kind": "<string>",
"code": "<string>",
"error": "<string>",
"error_id": "<string>",
"param": "<string>",
"status": 123
}Overview
Retrieve detailed information for a specific leak by its ID. This endpoint provides access to complete leak details including unmasked passwords after domain verification.Password Unmasking: Passwords are displayed unmasked after domain verification. Without verification, passwords appear as
***MASKED***.Authentication & Authorization
Access Control
- Personal leaks: Always accessible if the leak belongs to your email
- Employee/Customer leaks: Requires domain verification for the associated domain
- Password unmasking: Requires domain verification
Leak ID Format
The leak ID must be a 32-character MD5 hash (e.g.,b3652f2555841f7652badd9804859f4e).
Request Body
{
"leakid": "b3652f2555841f7652badd9804859f4e"
}
Response Examples
Successful Response
{
"success": true,
"data": {
"id": "b3652f2555841f7652badd9804859f4e",
"url": "https://facebook.com/login",
"username": "john.doe@example.com",
"password": "mypassword123",
"device_ip": "192.168.1.100",
"hostname": "JOHN-LAPTOP",
"os": "Windows 10 Pro",
"malware_path": "C:\\Users\\John\\AppData\\Roaming\\malware.exe",
"country": "United States",
"log_date": "2023-03-15T10:30:00Z",
"hardware_id": "HW-ABC123DEF456",
"domain": "example.com",
"email_domain": "example.com",
"fetched_at": "2023-03-16T08:00:00Z",
"status": "open"
}
}
Error Responses
Invalid Leak ID Format
{
"success": false,
"message": "Invalid leak ID format"
}
Leak Not Found
{
"success": false,
"message": "Leak not found"
}
Access Denied
{
"message": "Access denied: you don't have access to this leak"
}
Data Fields Explained
| Field | Description |
|---|---|
id | Unique 32-character MD5 hash identifier |
url | The website/service where credentials were compromised |
username | Username or email address (always unmasked if authorized) |
password | Password (masked/unmasked based on permissions) |
device_ip | IP address of the compromised device |
hostname | Computer/device hostname |
os | Operating system information |
malware_path | File path of the malware that captured the credentials |
country | Geographic location of the compromise |
log_date | When the credentials were captured |
hardware_id | Unique hardware identifier |
domain | Domain associated with this leak (for filtering) |
email_domain | Domain extracted from the email address |
fetched_at | When this leak was discovered/indexed |
status | Current status (open or fixed) |
Password Unmasking Rules
Passwords are unmasked after domain verification:| Leak Type | Password Access |
|---|---|
| Personal leaks | Always unmasked for the account owner |
| Employee leaks | Unmasked after domain verification |
| Customer leaks | Unmasked after domain verification |
***MASKED***.
Usage Examples
Get leak information
curl -X POST "https://api.projectdiscovery.io/v1/leaks/info" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"leakid": "b3652f2555841f7652badd9804859f4e"
}'
Security Considerations
Privacy Protection
- Access is strictly controlled based on domain verification
- All access attempts are logged for security auditing
Data Sensitivity
- Leak information contains sensitive credential data
- Ensure secure handling and storage of retrieved information
- Consider implementing additional encryption for stored leak details
Rate Limiting
- This endpoint may have rate limits to prevent abuse
- Implement proper error handling for rate limit responses
Authorizations
Body
application/json
32-character MD5 hash identifying the leak
Pattern:
^[a-fA-F0-9]{32}$Example:
"b3652f2555841f7652badd9804859f4e"
Was this page helpful?