- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks - I still get the padlock with the red slash when I go to 192.168.1.1, but Verizon says it's a browser quirk, and I should ignore it. I changed the password.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Updated 6/6/18
https://arstechnica.com/information-technology/2018/06/vpnfilter-malware-infecting-50000-devices-is-...
Asus Devices:
RT-AC66U (new)
RT-N10 (new)
RT-N10E (new)
RT-N10U (new)
RT-N56U (new)
RT-N66U (new)
D-Link Devices:
DES-1210-08P (new)
DIR-300 (new)
DIR-300A (new)
DSR-250N (new)
DSR-500N (new)
DSR-1000 (new)
DSR-1000N (new)
Huawei Devices:
HG8245 (new)
Linksys Devices:
E1200
E2500
E3000 (new)
E3200 (new)
E4200 (new)
RV082 (new)
WRVS4400N
Mikrotik Devices:
CCR1009 (new)
CCR1016
CCR1036
CCR1072
CRS109 (new)
CRS112 (new)
CRS125 (new)
RB411 (new)
RB450 (new)
RB750 (new)
RB911 (new)
RB921 (new)
RB941 (new)
RB951 (new)
RB952 (new)
RB960 (new)
RB962 (new)
RB1100 (new)
RB1200 (new)
RB2011 (new)
RB3011 (new)
RB Groove (new)
RB Omnitik (new)
STX5 (new)
Netgear Devices:
DG834 (new)
DGN1000 (new)
DGN2200
DGN3500 (new)
FVS318N (new)
MBRN3000 (new)
R6400
R7000
R8000
WNR1000
WNR2000
WNR2200 (new)
WNR4000 (new)
WNDR3700 (new)
WNDR4000 (new)
WNDR4300 (new)
WNDR4300-TN (new)
UTM50 (new)
QNAP Devices:
TS251
TS439 Pro
Other QNAP NAS devices running QTS software
TP-Link Devices:
R600VPN
TL-WR741ND (new)
TL-WR841N (new)
Ubiquiti Devices:
NSM2 (new)
PBE M5 (new)
Upvel Devices:
Unknown Models* (new)
ZTE Devices:
ZXHN H108N (new)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Break--Break....
Why isn't VERIZON itself not putting out more official information & guidance on this??
Seems like a pretty big deal, and this service provider is not exactly cheap.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Shanovan wrote:Break--Break....
Why isn't VERIZON itself not putting out more official information & guidance on this??
Seems like a pretty big deal, and this service provider is not exactly cheap.
Because it is not something affecting their routers or network.
why alarm folks over nothing?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Note that as of June 1, VZ has put out a rather vague VPNFilter advisory with a blanket recommendation to reboot, in broad context of "the various routers we provide." It neglects to say when or how often.
https://www.verizon.com/support/residential/announcements/important-information
Given the way VPNFilter is moving, I'd like to see much more from VZ, to the effect that they are actively monitoring and ensuring their device OEMs are working to keep their firmware ahead of the threat, including specific dates on which each VZ router brand-name has been remotely updated, if that is the case. Rebooting prior to such a date won't help much.
This appears to be a hostile nation-state attack, and it may only be a matter of time until they move across the less common devices.
https://blog.talosintelligence.com/2018/06/vpnfilter-update.html
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agree and am concerned with relative silence from Verizon on this VPNflter malware and othr security issues, which I hear about nearly every day in other forums. Internet security and communication with customers should be high priority and I have received nothing from Verizon about this. I would rather be proactive than try to clean up a mess.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
...and why is this flagged as solved??? it's actually evolving.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@msg160 wrote:...and why is this flagged as solved??? it's actually evolving.
Because the original question was solved to the original posters satisfaction.
the additional comments and solutions were just thread hyjacking.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I posted it solved because I was asking what Verizon equipment was or would be patched. At this point it appears the answer is none.
I appreciate all the other comments since I believe this is a major problem. All the ISPs should take responsibility for their customer equipment security. We are paying for this service.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Good People of this Verizon Customers' Community (which I just joined):
Aren't we all concerned about the FBI's warning that malware is infecting many American routers?! Are we following their advice to reboot our routers and update the firmware and strengthen our usernames and passwords? Here's an article from The New York Times:
https://www.nytimes.com/2018/05/27/technology/router-fbi-reboot-malware.html
Here's a follow-up story:
https://www.nytimes.com/2018/06/13/technology/personaltech/wi-fi-router-security.html
And here's advice from the follow-up:
■ If you use a router provided by a broadband provider like Comcast or Verizon, call the customer service department and ask whether your equipment has been updated with the latest firmware.
I've not called Verizon; I'm waiting for them to come to us. Verizon, are you reading this posting? Please acknowledge the threat and inform us fully of how you're dealing with it and tell us what steps we little guys need to do to stay safe on the Internet.
Ramsey NJ