Discovered a public live feed of a child’s bedroom via webcam; reached out to ROGERS.com ISP but received no response—what steps should I take next?

Urgent Concerns: Public Webcam Stream from a Child’s Bedroom – A Community Call to Action

Recently, I encountered a deeply troubling situation while browsing the internet. While exploring Shodan, a search engine for IoT devices, I discovered a public webcam stream originating from a young child’s bedroom. Alarmingly, the stream was linked to an ISP customer in Canada, specifically Rogers Communications. This discovery raised considerable concern for me as a parent and prompted me to seek guidance about how to address it.

Initial Attempts to Address the Issue

Upon realizing the potential danger, my first step was to contact Rogers’ customer support team. After an exhausting conversation that lasted over thirty minutes, I spoke with a representative who ultimately referred me to a supervisor. Unfortunately, instead of providing me with useful solutions, the supervisor informed me that I could escalate the matter to local authorities either in Austria, where I reside, or in Canada.

Feeling exasperated with their dismissive approach, I shared my experience through various channels, hoping for better assistance. At this point, I believe the owners of the webcam may not have been aware of their device’s public exposure, which makes this situation even more pressing.

Updates on the Situation

I made several attempts to take further action. I reached out to the appropriate email address at Rogers, as well as the Office of the Privacy Commissioner of Canada and the Canadian Centre for Cyber Security. Additionally, I tried contacting the Canadian authorities via the phone number provided by Rogers, but I faced difficulties getting through.

Fortunately, I received some positive news on January 26 – the owner of the webcam has been successfully contacted, and the stream is now protected by a password. I also received an email from Rogers confirming that my concerns have been escalated, and they will be reaching out to the webcam owner as well.

A Call to Action for Concerned Citizens

I want to take this opportunity to express my gratitude for the outpouring of support from the community. It’s heartening to see people reach out with suggestions and assistance. While I may not have found immediate success through traditional channels, this experience has highlighted the effectiveness of collective voices in addressing serious issues.

For anyone who finds themselves in a similar situation, I encourage you to take the following steps:

  1. Document Everything: Keep a record of your communications, including chat transcripts with customer support and any public URLs you discover.
  2. Reach Out to Proper Authorities: If a situation involves serious privacy concerns

Share this content:

One Comment

  1. Hello,

    It’s encouraging to see your proactive approach in addressing this serious privacy concern. When dealing with such issues involving publicly accessible IoT devices or webcams, here are some additional steps and precautions you can consider:

    • Report to Internet Service Provider (ISP): Since Rogers has already been contacted, ensure you document all communication and request that they escalate the issue internally. Some ISPs have dedicated teams for security and privacy breaches.
    • Contact Internet Abuse Authorities: You can report the incident to organizations like IC3 (Internet Crime Complaint Center) or similar governmental cybercrime units in Canada and Austria, depending on jurisdiction.
    • Notify Cybersecurity Organizations: Consider reporting the exposure to cybersecurity organizations or platforms such as Cybertip.ca.
    • Secure the Webcam Device: If you are the owner of the device or have contact with the owner, advise them to update the device firmware, change default passwords, and disable remote access until the security breach is resolved.
    • Public Awareness and Reporting: Sharing your findings responsibly can help protect others. Consider

Leave a Reply to [email protected] Cancel reply

Your email address will not be published. Required fields are marked *