Attributed metadata history
Up to 100 retained publisher events per page for 830a59ad589b2103a818ed9f7c57c19990fb773e14d3a6502090c30eef25b240. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_ad89769b9e64591ab5
observed · 2026-10-12 14:01:03 UTC
available
Fingerprint: 05d146f940ea021a0ff67bda626eeffcdf1f2ccbc0f3c3114fff19b0a80eeaf4
intelligence_src_ad89769b9e64591ab5
observed · 2026-10-12 14:01:03 UTC
One important player in the PPPP protocol business is VStarcam. At the very least they’ve already accumulated an impressive portfolio of security issues. Like exposing system configuration including access password unprotected in the Web UI (discovered by multiple people independently from the look of it). Or the open telnet port accepting hardcoded credentials (definitely discovered by lots of people independently). In fact, these cameras have been seen used as part of a botnet, likely thanks to some documented vulnerabilities in their user interface. Is that a thing of the past? Are there updates fixing these issues? Which devices can be updated? These questions are surprisingly hard to answer. I found zero information on VStarcam firmware versions, available updates or security fixes. In fact, it doesn’t look like they ever even acknowledged learning about the existence of these vulnerabilities. No way around downloading these firmware updates and having a look for myself. With surprising results. First of all: there are lots of firmware updates. It seems that VStarcam accumulated a huge number of firmware branches. And even though not all of them even have an active or down
Fingerprint: ee89c9aee33f02d991d7e16c2f0593e07699ebd8f6dc97ba859552446f7e2028