# AWS GuardDuty False Positive on OpenDSN IP | Cycle.io

Canonical URL: https://cycle.io/community/threads/6a973969c6fe06e5addb0178/aws-guardduty-false-positive-on-opendsn-ip

## AWS GuardDuty False Positive on OpenDSN IP

[announcement](https://cycle.io/community/categories/announcement)

According to reports from Cycle customers, sometime after 3 pm EST today, the service AWS GuardDuty started to flag DNS traffic from Cycle servers to Cisco's OpenDNS resolver (`208.67.222.222`) as botnet command and control activity.

This report is a false positive and nothing on your infrastructure is pointing to a compromise based on this specific event in GuardDuty.

### What You're Likely Seeing

What's being reported is a high-severity alert for something that looks like this.

-   Type - Backdoor:EC2/C&CActivity.B
-   Threat List - Amazon Active Threat Defense
-   Threat Name - suspicious:cmdctrl/botnet
-   Remote IP - 208.67.222.222 (TCP/53)

### Why Cycle talks to that IP

The discovery service in the environments use upstream resolvers for egress traffic:

-   `8.8.8.8` / `8.8.4.4` - Google
-   `1.1.1.1` / `1.0.0.1` - Cloudflare
-   `9.9.9.9` - Quad9
-   `208.67.222.222` - Cisco OpenDNS

  

These providers are deliberately rotated across.

We are confident this is a false positive due to the IP thats flagged being a trusted OpenDNS endpoint provided by Cisco. It is absolutely not botnet infrastructure.

  

-   Brandon Cummings...
    
    This happened to us around 330pm ET - AWS GuardDuty started alerting of critical 8 and 9 alerts.
    
-   Jake Warner...
    
    Looks like these reports only happened for 30-45 min overall. AWS must've accidentally added the IP before removing it.
    

#### Join the conversation

Sign in with your Cycle account to reply to this thread.

Sign in

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
