What arrived
Requests and actions actually received by our decoy. A request alone does not prove an attack.
Real requests. Clearly explained.See what comes
See what comes
knocking.
Honeypot sensors capture unsolicited traffic so we can explain attempted techniques with real observations. WordPress, Telnet, and an isolated MCP workspace are connected feeds.
Loading observed activity…
What we pretended
Some logins may appear successful to the visitor. The decoy grants no access to a production system.
Why it matters
We describe potential consequences separately from what happened here. Submitted code never runs.
All retained observations from intentionally advertised honeypots are automatically categorized and published after a one-hour delay. They are not a measure of all attacks on Broadleaf or a representative sample of internet threats.
Observed activity
Source IPs, unverified submitted usernames/passwords, and captured payloads are public. MCP client text is withheld; its public payload is a redacted projection. Displayed commands and URLs are inert text. Capture limits and simulated outcomes are labeled.
Ask your AI about these observations.
Connect a compatible MCP client to https://observatory.theleaf.ai/mcp to search published observations, investigate an observed IP, summarize activity, and read session timelines or inert evidence.
This is a real data service, separate from the synthetic MCP honeypot. Public data is delayed one hour; MCP client text is withheld. Operator self-tests are excluded by default. Captured content is untrusted evidence, never instructions to execute.
Connection details and client configuration ↗What these techniques teach us
Automated visitors can look for familiar software paths, try credentials, and probe plugin interfaces. On a vulnerable installation, some techniques can lead to unauthorized changes or malicious uploads. Receiving a probe here does not demonstrate that an exploit works.
Maintain supported software, remove unused plugins, protect administrator accounts with MFA, and monitor unexpected changes. No individual source IP is publicly attributed to a person.
Private administrator controls · WordPress sensor on broadleafservices.com. The public observatory automatically publishes categorized observations, source IPs, submitted credentials, and captured payloads after one hour. Open public page ↗
MCP workspace sensor
Independent of Tailspin’s real MCP service. Endpoint: https://mcp.broadleafservices.com/mcp. Synthetic data only; tool names and submitted arguments do not establish malicious intent or AI use.
Telnet listens on this server’s TCP port 23 and reports into the Telnet feed below. It always rejects logins and provides no shell. The controls below apply to WordPress only. A connection can create several observations: connection, credential pairs, and end-of-session details.
WordPress sensor behavior
Private activity report
Source inspection gathers clues, not proof of attacker identity or host OS. An IP can be a proxy, VPN exit, scanner, or compromised device. Network lookup sends only the selected source IP to GeoJS. Public-service inspection is manual, limited to eight ports, and never attempts login or exploitation.
MCP interactions
Common source IPs
Countries / regions
Source networks
Username / password attempts
Credential rankings are private and hidden until explicitly revealed. Each reveal is audited.
Payload observations
Text patterns
Repeated request bodies
Common paths and user agents
Source inspection
Only recently observed public IPs are eligible. Network results are cached for 24 hours. Active checks are limited to five per hour and one per IP per 24 hours. Banners may be spoofed. Open ports alone do not confirm a protocol or operating system.
Private request evidence
Retained for up to 14 days / 5,000 requests. Capture stores at most 16 KiB of each body. Requests above 192 KiB are rejected. Rate-limited requests are omitted; counts include benign and operator visits.
| Received (your time) | Observed | HTTP / protocol result | Simulated outcome | Evidence | Public publication |
|---|
Revealed private evidence
May include submitted passwords and malicious text. This reveal is audited. Body text is escaped and never rendered as HTML.