Overview
Theconfluence search command performs full-text searches across Confluence content, including pages, comments, and attachments. This command supports wildcard searches, making it particularly powerful for discovering specific patterns like URLs, credentials, API keys, email addresses, and other sensitive information embedded in Confluence content.
This is one of AtlasReaper’s most versatile reconnaissance commands, enabling targeted discovery of specific content without enumerating all pages.
Syntax
Required Parameters
The base URL of the Confluence instance (e.g.,
https://example.atlassian.net)The search query string. Supports wildcards (
*) for flexible pattern matching (e.g., http*example.com*, password*, api_key*)Optional Parameters
Authentication cookie (
cloud.session.token or tenant.session.token). If omitted, the command will attempt anonymous access (if enabled on the target)Return all search results, overriding the limit parameter
Maximum number of search results to return. Default is 250
Save command output to a specified file for offline analysis and processing
Examples
- Basic Keyword Search
- Wildcard URL Pattern
- API Key Discovery
- Credential Hunting
- Internal Domain Discovery
- SSH/Config File Hunt
- Cloud Service Credentials
- VPN and Remote Access
Use Cases
Red Team Perspectives
Red Team Perspectives
Credential and Secret Discovery
- Find credentials hardcoded in documentation (passwords, API keys, tokens)
- Locate service account credentials and authentication details
- Discover SSH keys, certificates, and other authentication materials
- Hunt for cloud provider credentials (AWS, Azure, GCP access keys)
- Find database connection strings with embedded credentials
- Discover internal domains, hostnames, and IP addresses
- Identify network architecture and topology information
- Find documentation about internal services and applications
- Locate VPN, remote access, and jump host information
- Map infrastructure through documented server names and addresses
- Search for specific technologies, products, or services in use
- Find vulnerability documentation and security assessments
- Discover incident response procedures and playbooks
- Locate security tool configurations and detection capabilities
- Identify administrative procedures and privileged access methods
- Gather information about projects, initiatives, and organizational priorities
- Find communication patterns and organizational terminology
- Identify key personnel and their roles from documentation
- Discover upcoming events or changes to reference in pretexts
- Locate email addresses and contact information
- Search for documentation about administrative access
- Find runbooks that may contain privileged credentials
- Discover backup and recovery procedures with sensitive information
- Locate documentation about security controls and monitoring gaps
- Identify service accounts and their purposes
- Find documentation about system interconnections and trust relationships
- Discover shared credentials across multiple systems
- Locate network segmentation and firewall rule documentation
- Identify systems with known vulnerabilities documented in Confluence
Blue Team Perspectives
Blue Team Perspectives
Security Posture Assessment
- Search for hardcoded credentials in documentation (proactive remediation)
- Identify API keys, tokens, and secrets that should be in vaults
- Find sensitive infrastructure information that shouldn’t be documented
- Discover compliance violations (PII, PHI, financial data in Confluence)
- Audit for security misconfigurations documented in pages
- Identify regulated data stored inappropriately in Confluence
- Find personal information (SSN, credit cards, health data)
- Discover financial information requiring protection
- Locate intellectual property and trade secrets
- Audit for data classification policy violations
- Search for indicators of compromise documented by attackers
- Find suspicious content added by compromised accounts
- Identify malicious URLs or domains embedded in pages
- Discover evidence of reconnaissance or enumeration activities
- Hunt for command and control communication artifacts
- During compromise, search for what information attacker may have discovered
- Identify credentials that need rotation based on exposure
- Determine scope of information disclosure
- Find evidence of attacker activity in page content
- Prioritize remediation based on search results
- Monitor for suspicious search queries (credential-related terms, wildcard patterns)
- Alert on bulk searches (high volume of search API calls)
- Track accounts performing searches they don’t typically conduct
- Identify searches for security tools, detection systems, or monitoring
- Flag searches from external IP addresses or unusual geolocations
- Search for documented vulnerabilities and security issues
- Identify systems with known weaknesses
- Find security assessment results and penetration test reports
- Discover security debt and unpatched systems
- Audit documentation of security exceptions and accepted risks
Output
The command returns search results with context about matches:- Page title and page ID
- Space key and space name
- Excerpt showing the matched content with context
- Match relevance score
- Last modified date
- URL to the page
- Content type (page, blogpost, comment, attachment)
Detection Considerations
Confluence Audit Logs- All search queries are logged with the search terms used
- Audit logs include username, timestamp, query string, and IP address
- Sensitive search terms (password, credential, api_key) may trigger alerts
- Security teams may monitor for credential-related search terms
- Wildcard searches with suspicious patterns are particularly noticeable
- Bulk searches (many queries in short time) create distinct patterns
- UEBA solutions flag unusual search behavior
- Searches for security-related terms by non-security personnel are suspicious
- Accounts that don’t typically use search suddenly performing many queries
- Search patterns inconsistent with the user’s role
- Search API calls generate web server logs
- High-volume search operations may trigger rate limiting
- Automated search patterns differ from human search behavior
- Searches returning sensitive content may trigger DLP alerts
- Security teams may receive notifications when sensitive pages are accessed via search
- Search results containing regulated data may be monitored
OPSEC Considerations
-
Query Selection and Phrasing
- Avoid obviously malicious search terms (password, credential, api_key in isolation)
- Use more natural search queries when possible
- Consider business context that would justify the search
- Be aware that search queries are logged and may be reviewed
-
Wildcard Usage Strategy
- Wildcards are powerful but create distinctive search patterns
- Overly broad wildcards may return too many results and take too long
- Balance specificity with operational security
- Consider whether wildcard searches are more suspicious than specific queries
-
Timing and Rate
- Perform searches during business hours when activity is normal
- Space out searches to mimic human research patterns
- Avoid rapid-fire searches that indicate automated enumeration
- Consider the compromised account’s typical work schedule
-
Account Context
- Ensure search queries match the account’s role and responsibilities
- Security/IT accounts searching for credentials is less suspicious
- Marketing accounts searching for infrastructure is highly suspicious
- Consider whether the search fits the user’s job function
-
Scope and Volume
- Use targeted searches rather than blanket reconnaissance
- Limit result sets when possible to reduce API call volume
- Avoid excessive use of —all flag
- Balance intelligence requirements with operational security
-
Output Management
- Always use —output for sensitive searches to avoid re-running them
- Process results offline to minimize interactive time
- Secure output files as they may contain highly sensitive information
- Delete temporary files securely after operations
-
Result Processing
- Review search results to identify false positives
- Prioritize high-value results for further investigation
- Use search results to guide targeted page/attachment access
- Avoid accessing every search result (may be logged)
-
Alternative Approaches
- Consider whether enumeration + offline grep is less conspicuous
- Evaluate if social engineering could obtain the same information
- Use public sources before internal searches when possible
- Determine if search is necessary given existing intelligence
-
Operational Planning
- Plan search queries carefully before execution
- Have a clear intelligence requirement driving each search
- Understand what you’re looking for and why
- Map search results to next-stage operations (download, exfiltration)
-
Legal and Ethical Considerations
- Ensure proper authorization for search operations
- Be aware that searches may expose sensitive personal information
- Consider privacy implications of search queries
- Document approval and scope for offensive operations
Related Commands
- confluence listpages - Alternative reconnaissance method via enumeration
- confluence download - Download attachments identified through search
- confluence listattachments - Find attachments after identifying target pages via search
- confluence listspaces - Identify spaces before conducting targeted searches
- jira searchissues - Similar search functionality for Jira