{"id":45899,"date":"2026-10-01T04:41:54","date_gmt":"2026-10-01T02:41:54","guid":{"rendered":"https:\/\/hotelnetsolutions.de\/security-notice\/"},"modified":"2026-11-04T02:34:18","modified_gmt":"2026-11-04T01:34:18","slug":"security-notice","status":"publish","type":"page","link":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/","title":{"rendered":"Security notice"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-page\" data-elementor-id=\"45899\" class=\"elementor elementor-45899 elementor-45812\" data-elementor-settings=\"{&quot;ha_cmc_init_switcher&quot;:&quot;no&quot;}\" data-elementor-post-type=\"page\">\n\t\t\t\t\t\t<section class=\"ob-is-breaking-bad elementor-section elementor-top-section elementor-element elementor-element-78619ef elementor-section-full_width elementor-section-content-middle elementor-section-height-default elementor-section-height-default\" data-id=\"78619ef\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-top-column elementor-element elementor-element-1d307e33\" data-id=\"1d307e33\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-35c90fb5 ob-has-background-overlay elementor-widget elementor-widget-image\" data-id=\"35c90fb5\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_animation&quot;:&quot;none&quot;,&quot;_animation_mobile&quot;:&quot;none&quot;,&quot;_ob_photomorph_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img fetchpriority=\"high\" decoding=\"async\" width=\"1280\" height=\"1280\" src=\"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing-1280x1280.jpg\" class=\"attachment-medium_square size-medium_square wp-image-45832\" alt=\"\" srcset=\"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing-1280x1280.jpg 1280w, https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing-769x768.jpg 769w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/>\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-top-column elementor-element elementor-element-3aba2d49\" data-id=\"3aba2d49\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-32212d3 ob-has-background-overlay elementor-widget elementor-widget-button\" data-id=\"32212d3\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_butterbutton_use_it&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-button-wrapper\">\n\t\t\t\t\t<a class=\"elementor-button elementor-button-link elementor-size-sm\" href=\"#\">\n\t\t\t\t\t\t<span class=\"elementor-button-content-wrapper\">\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-button-text\">Security notice<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-45c75e3 ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-heading\" data-id=\"45c75e3\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_harakiri_text_clip&quot;:&quot;none&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Phishing with booking data<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-b715a06 elementor-button-success elementor-widget__width-auto ob-has-background-overlay elementor-widget elementor-widget-button\" data-id=\"b715a06\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_butterbutton_use_it&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-button-wrapper\">\n\t\t\t\t\t<a class=\"elementor-button elementor-button-link elementor-size-sm\" href=\"#current-news\">\n\t\t\t\t\t\t<span class=\"elementor-button-content-wrapper\">\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-button-text\">Current update<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7abbe9d elementor-button-info elementor-widget__width-auto ob-has-background-overlay elementor-widget elementor-widget-button\" data-id=\"7abbe9d\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_butterbutton_use_it&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-button-wrapper\">\n\t\t\t\t\t<a class=\"elementor-button elementor-button-link elementor-size-sm\" href=\"#fragen\">\n\t\t\t\t\t\t<span class=\"elementor-button-content-wrapper\">\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-button-text\">FAQ<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"ob-is-breaking-bad elementor-section elementor-top-section elementor-element elementor-element-e481439 elementor-section-height-min-height elementor-section-boxed elementor-section-height-default elementor-section-items-middle\" data-id=\"e481439\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-25 elementor-top-column elementor-element elementor-element-1d2746a\" data-id=\"1d2746a\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap\">\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-top-column elementor-element elementor-element-864a400\" data-id=\"864a400\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-9bc908b elementor-align-center ob-has-background-overlay elementor-widget elementor-widget-button\" data-id=\"9bc908b\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_butterbutton_use_it&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-button-wrapper\">\n\t\t\t\t\t<a class=\"elementor-button elementor-button-link elementor-size-sm\" href=\"#\">\n\t\t\t\t\t\t<span class=\"elementor-button-content-wrapper\">\n\t\t\t\t\t\t<span class=\"elementor-button-icon\">\n\t\t\t\t<i aria-hidden=\"true\" class=\"far fa-dot-circle\"><\/i>\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-button-text\">Last updated on October 7th, 2026<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-8248569 ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-text-editor\" data-id=\"8248569\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_postman_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>A technical vulnerability at HotelNetSolutions was exploited, which allowed unauthorised access to booking information. In connection with the incident, booking information is being used for very convincing phishing messages to hotel guests. The identified vulnerability was closed on 19 September 2026; work on the incident is continuing.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-25 elementor-top-column elementor-element elementor-element-1374fcd\" data-id=\"1374fcd\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap\">\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"ob-is-breaking-bad elementor-section elementor-top-section elementor-element elementor-element-15b78a9 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"15b78a9\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-47fd526\" data-id=\"47fd526\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-f230ca5 elementor-button-info ob-has-background-overlay elementor-widget elementor-widget-button\" data-id=\"f230ca5\" data-element_type=\"widget\" data-e-type=\"widget\" id=\"current-news\" data-settings=\"{&quot;_ob_butterbutton_use_it&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-button-wrapper\">\n\t\t\t\t\t<a class=\"elementor-button elementor-button-link elementor-size-sm\" href=\"#\">\n\t\t\t\t\t\t<span class=\"elementor-button-content-wrapper\">\n\t\t\t\t\t\t\t\t\t<span class=\"elementor-button-text\">Current update<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-12d3aa0 ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-heading\" data-id=\"12d3aa0\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_harakiri_text_clip&quot;:&quot;none&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">What applies today<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<section class=\"ob-is-breaking-bad ob-bb-inner elementor-section elementor-inner-section elementor-element elementor-element-9f3962c elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"9f3962c\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-wider\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-inner-column elementor-element elementor-element-3d197ae\" data-id=\"3d197ae\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<section class=\"ob-is-breaking-bad ob-bb-inner elementor-section elementor-inner-section elementor-element elementor-element-fcf12b7 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"fcf12b7\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-narrow\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-inner-column elementor-element elementor-element-44fa7ce\" data-id=\"44fa7ce\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-4ece58a ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-text-editor\" data-id=\"4ece58a\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_postman_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p><span style=\"display: block; margin-bottom: 4px; font-size: 22px; font-weight: 500;\">October 30th, 2026<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-inner-column elementor-element elementor-element-2b30d33\" data-id=\"2b30d33\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-421fbda elementor-widget__width-initial ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-text-editor\" data-id=\"421fbda\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_postman_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<h3 data-i18n=\"current.heading\">Instructions for reporting phishing incidents<\/h3><p data-i18n=\"current.p1\">The underlying security vulnerability was closed on September 19, 2026, at approximately 2:00 PM. <strong>Please therefore only report phishing cases to us where the transaction in question took place after September 19, 2026.<\/strong> We will review these cases promptly.<\/p><p data-i18n=\"current.p2\">For earlier bookings, guests may still receive phishing messages, as data that has already been compromised can be misused at a later time &#8211; for instance, shortly before arrival or after departure. There is no need to report these instances again.<\/p><p data-i18n=\"current.p2\">The entire hotel industry is currently experiencing an increased volume of cyberattacks and phishing attempts. Consequently, not every fraudulent message can be attributed to the security incident at HotelNetSolutions.<\/p><p data-i18n=\"current.p2\">Please continue to keep your guests transparently informed about potential phishing messages and raise their awareness regarding fraudulent attempts to make contact.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"ob-is-breaking-bad ob-bb-inner elementor-section elementor-inner-section elementor-element elementor-element-b8bd49b elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"b8bd49b\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-wider\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-inner-column elementor-element elementor-element-e2c3e6b\" data-id=\"e2c3e6b\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<section class=\"ob-is-breaking-bad ob-bb-inner elementor-section elementor-inner-section elementor-element elementor-element-8c41753 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"8c41753\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-narrow\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-inner-column elementor-element elementor-element-3571a77\" data-id=\"3571a77\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-24df389 ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-text-editor\" data-id=\"24df389\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_postman_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p><span style=\"display: block; margin-bottom: 4px; font-size: 22px; font-weight: 500;\">October 7th, 2026<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-50 elementor-inner-column elementor-element elementor-element-b49e367\" data-id=\"b49e367\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-cc80372 elementor-widget__width-initial ob-harakiri-inherit ob-has-background-overlay elementor-widget elementor-widget-text-editor\" data-id=\"cc80372\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_use_harakiri&quot;:&quot;yes&quot;,&quot;_ob_harakiri_writing_mode&quot;:&quot;inherit&quot;,&quot;_ob_postman_use&quot;:&quot;no&quot;,&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<h3 data-i18n=\"current.heading\">External cybersecurity specialist selected<\/h3><p data-i18n=\"current.p1\">We have selected a company specialising in cybersecurity and incident response. The scope of the independent investigation and security review is currently being agreed.<\/p><p data-i18n=\"current.p2\">The aim is to independently investigate the known attack path, identify additional risks and derive further technical and organisational measures.<\/p><p data-i18n=\"current.p2\">The incident has been reported to the State Criminal Police Office (Landeskriminalamt).<\/p><div class=\"fact\" style=\"background: white; border-radius: 18px; padding: 18px 22px; margin: 22px 0;\" data-i18n=\"current.period\"><p><strong style=\"margin-bottom: 2px; font-size: 13px; font-weight: 500; letter-spacing: 0.02em; text-transform: uppercase; color: rgba(0, 14, 7, 0.58);\">Time period<\/strong><br \/>When the unauthorised access began and its full extent have still not been conclusively determined. Reconstructing the timeline is part of the ongoing investigation.<\/p><\/div><div class=\"fact\" style=\"background: white; border-radius: 18px; padding: 18px 22px; margin: 22px 0;\" data-i18n=\"current.payment\"><p><strong style=\"margin-bottom: 2px; font-size: 13px; font-weight: 500; letter-spacing: 0.02em; text-transform: uppercase; color: rgba(0, 14, 7, 0.58);\">Payment data<\/strong><br \/>Based on the information currently available, there is no indication that credit card or other payment data was exfiltrated through the identified vulnerability.<\/p><\/div><div class=\"fact\" style=\"background: white; border-radius: 18px; padding: 18px 22px; margin: 22px 0;\" data-i18n=\"current.payment\"><p><strong style=\"margin-bottom: 2px; font-size: 13px; font-weight: 500; letter-spacing: 0.02em; text-transform: uppercase; color: rgba(0, 14, 7, 0.58);\">Current phishing variant<\/strong><br \/>In addition to phishing messages sent before arrival, for example about check-in or payments, we are currently also seeing emails sent after departure about alleged additional charges or refunds. Links in such messages should not be opened without checking them first.<\/p><\/div><p data-i18n=\"current.p4\">We will report new reliable findings and any resulting measures on this page.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"ob-is-breaking-bad elementor-section elementor-top-section elementor-element elementor-element-14fc39a elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"14fc39a\" data-element_type=\"section\" data-e-type=\"section\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;_ob_bbad_use_it&quot;:&quot;yes&quot;,&quot;_ob_bbad_sssic_use&quot;:&quot;no&quot;,&quot;_ob_glider_is_slider&quot;:&quot;no&quot;}\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-0b79b16\" data-id=\"0b79b16\" data-element_type=\"column\" data-e-type=\"column\" data-settings=\"{&quot;_ob_bbad_is_stalker&quot;:&quot;no&quot;,&quot;_ob_teleporter_use&quot;:false,&quot;_ob_column_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_column_has_pseudo&quot;:&quot;no&quot;}\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-be2a7f0 ob-has-background-overlay elementor-widget elementor-widget-html\" data-id=\"be2a7f0\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;_ob_perspektive_use&quot;:&quot;no&quot;,&quot;_ob_poopart_use&quot;:&quot;yes&quot;,&quot;_ob_shadough_use&quot;:&quot;no&quot;,&quot;_ob_allow_hoveranimator&quot;:&quot;no&quot;,&quot;_ob_widget_stalker_use&quot;:&quot;no&quot;}\" data-widget_type=\"html.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<!-- HNS security-incident landing content \u2013 Elementor single-file embed.\n     Extracted from the original main .wrap, with #aktuell intentionally excluded.\n     Language: \/en\/ => English; otherwise German. ?lang=en\/de is retained as a testing override. -->\n<div id=\"hns-phishing-landing\">\n  <style>\n    \/* Landingpage \u201ePhishing mit Buchungsdaten\u201c.\n   Angelehnt an hotelnetsolutions.de: Schrift Whyte, Tintenschwarz #000E07, Seitengrund #F4F4F4,\n   B\u00fchne mit Bildfl\u00e4che links (obere rechte Ecke 40px rund), Inhaltsfl\u00e4chen mit Mint-Verlauf und\n   30px Radius, Pillen, Orange #FF6800 als Akzent, dunkler Fu\u00df. *\/\n\n    #hns-phishing-landing {\n      --font: Whyte, Helvetica, Arial, sans-serif;\n      --ink: #000e07;\n      --ink-muted: rgba(0, 14, 7, 0.58);\n      --line: rgba(0, 14, 7, 0.12);\n      --page: #f4f4f4;\n      --white: #ffffff;\n      --panel: #f1f5f5;\n      --mint: #e1eee6;\n      --mint-strong: #d3e6da;\n      \/* HNS-Status (aktuelle Meldung, Ma\u00dfnahmen): beginnt schon links in Mint, damit sich die Kante vom\n     grauen Seitengrund abhebt. *\/\n      --status-gradient: linear-gradient(135deg, #e7f2eb 0%, #d5e9dc 100%);\n      --accent: #ff6800;\n      --accent-soft: #fff1e6;\n      --wrap: 1200px;\n    }\n\n    #hns-phishing-landing *,\n    #hns-phishing-landing *::before,\n    #hns-phishing-landing *::after {\n      box-sizing: border-box;\n    }\n\n    #hns-phishing-landing {\n      scroll-behavior: smooth;\n      scroll-padding-top: 100px;\n    }\n\n    #hns-phishing-landing {\n      margin: 0;\n      color: var(--ink);\n      font-family: var(--font);\n      font-size: 17px;\n      line-height: 1.55;\n      -webkit-font-smoothing: antialiased;\n    }\n\n    #hns-phishing-landing a {\n      color: inherit;\n      text-underline-offset: 4px;\n    }\n\n    #hns-phishing-landing a:focus-visible,\n    #hns-phishing-landing button:focus-visible,\n    #hns-phishing-landing summary:focus-visible {\n      outline: 2px solid var(--accent);\n      outline-offset: 3px;\n      border-radius: 6px;\n    }\n\n    #hns-phishing-landing .wrap {\n      max-width: var(--wrap);\n      margin: 0 auto;\n      padding: 0;\n    }\n\n    #hns-phishing-landing .eyebrow {\n      display: inline-block;\n      padding: 5px 11px;\n      border-radius: 20px;\n      background: var(--ink);\n      color: var(--white);\n      font-size: 12px;\n      line-height: 1.2;\n    }\n\n    \/* ---------- Kopf (Nachbildung der Website-Navigation) ---------- *\/\n\n    #hns-phishing-landing .site-header {\n      position: sticky;\n      top: 0;\n      z-index: 10;\n      background: rgba(247, 247, 247, 0.96);\n      border-bottom: 1px solid var(--line);\n      backdrop-filter: blur(6px);\n    }\n\n    #hns-phishing-landing .site-header .wrap {\n      display: flex;\n      align-items: center;\n      gap: 16px;\n      height: 85px;\n    }\n\n    #hns-phishing-landing .logo {\n      display: block;\n      font-size: 19px;\n      font-weight: 700;\n      line-height: 0.82;\n      letter-spacing: -0.02em;\n      text-decoration: none;\n    }\n\n    #hns-phishing-landing .site-header__page {\n      margin-left: 4px;\n      padding-left: 16px;\n      border-left: 1px solid var(--line);\n      line-height: 1.25;\n    }\n\n    #hns-phishing-landing .site-header__page strong {\n      display: block;\n      font-size: 17px;\n      font-weight: 500;\n    }\n\n    #hns-phishing-landing .site-header__page span {\n      font-size: 14px;\n      color: var(--ink-muted);\n    }\n\n    #hns-phishing-landing .site-nav {\n      display: flex;\n      align-items: center;\n      gap: 30px;\n      margin-left: auto;\n      font-size: 14px;\n    }\n\n    #hns-phishing-landing .site-nav__cta {\n      padding: 9px 21px;\n      border-radius: 40px;\n      background: var(--accent);\n      color: var(--white);\n      font-weight: 500;\n    }\n\n    \/* Sprachwahl DE \/ EN rechts neben der Navigation \u2013 wie die Sprachumschaltung von\n   hotelnetsolutions.de, dort mit Flaggen; hier als K\u00fcrzel. Bleibt auch auf schmalen Bildschirmen\n   sichtbar. Gleicher Block in beiden Repos (Landingpage und Generator). *\/\n    #hns-phishing-landing .site-lang {\n      display: flex;\n      align-items: center;\n      gap: 2px;\n      margin-left: 18px;\n      font-size: 13px;\n      line-height: 1;\n    }\n\n    #hns-phishing-landing .site-lang a {\n      padding: 8px 6px;\n      border-radius: 6px;\n      color: var(--ink-muted);\n      font-weight: 500;\n      text-decoration: none;\n    }\n\n    #hns-phishing-landing .site-lang a:hover {\n      color: var(--ink);\n    }\n\n    #hns-phishing-landing .site-lang a[aria-current=\"true\"] {\n      color: var(--ink);\n      text-decoration: underline;\n      text-decoration-thickness: 1.5px;\n      text-underline-offset: 5px;\n    }\n\n    #hns-phishing-landing .site-lang a:focus-visible {\n      outline: 2px solid var(--accent);\n      outline-offset: 1px;\n    }\n\n    \/* ---------- B\u00fchne ---------- *\/\n\n    \/* Wie auf den Produktseiten (z. B. \/produkte\/onepagebooking\/): Verlauf \u00fcber die volle Breite,\n   Bild links b\u00fcndig mit abgerundeter oberer rechter Ecke, rechts nur Etikett, \u00dcberschrift, Buttons. *\/\n    #hns-phishing-landing .stage {\n      padding-top: 50px;\n      background: linear-gradient(90deg, #eae8e8 0%, #d7e9e0 100%);\n    }\n\n    \/* Wie auf hotelnetsolutions.de gemessen: Bild = halbe Fensterbreite minus 80 px, quadratisch\n   (1440 \u2192 640 \u00d7 640, 1920 \u2192 880 \u00d7 880); Text 60 px daneben, h\u00f6chstens 610 px breit. *\/\n    #hns-phishing-landing .stage__inner {\n      display: grid;\n      grid-template-columns: calc(50% - 80px) minmax(0, 1fr);\n      align-items: center;\n      gap: 60px;\n    }\n\n    #hns-phishing-landing .stage__image {\n      display: block;\n      width: 100%;\n      aspect-ratio: 1 \/ 1;\n      height: auto;\n      object-fit: cover;\n      object-position: 50% 60%;\n      border-radius: 0 40px 0 0;\n    }\n\n    #hns-phishing-landing .stage__text {\n      max-width: 610px;\n      padding: 40px 40px 40px 0;\n    }\n\n    #hns-phishing-landing .stage__label {\n      display: inline-block;\n      padding: 6px 12px;\n      border-radius: 20px;\n      background: rgba(255, 255, 255, 0.55);\n      font-size: 12px;\n      line-height: 1.2;\n    }\n\n    #hns-phishing-landing .stage h1 {\n      margin: 22px 0 30px;\n      font-size: 65px;\n      font-weight: 500;\n      line-height: 1;\n      letter-spacing: -0.01em;\n      text-wrap: balance;\n    }\n\n    #hns-phishing-landing .stage__actions {\n      display: flex;\n      flex-wrap: wrap;\n      gap: 10px;\n    }\n\n    #hns-phishing-landing .button {\n      display: inline-flex;\n      align-items: center;\n      height: 36px;\n      padding: 0 16px;\n      border: 1px solid var(--ink);\n      border-radius: 40px;\n      font-size: 13px;\n      text-decoration: none;\n      transition:\n        background-color 0.15s,\n        color 0.15s;\n    }\n\n    #hns-phishing-landing .button:hover {\n      background: var(--ink);\n      color: var(--white);\n    }\n\n    #hns-phishing-landing .button--dark {\n      background: var(--ink);\n      color: var(--white);\n    }\n\n    #hns-phishing-landing .button--dark:hover {\n      background: transparent;\n      color: var(--ink);\n    }\n\n    \/* Einleitung zentriert unter der B\u00fchne, wie der erste Abschnitt der Produktseiten *\/\n    #hns-phishing-landing .intro {\n      padding: 110px 0 0;\n      text-align: center;\n    }\n\n    #hns-phishing-landing .intro__label {\n      display: inline-flex;\n      align-items: center;\n      gap: 8px;\n      padding: 7px 14px;\n      border-radius: 20px;\n      background: #ededed;\n      font-size: 12px;\n      font-weight: 500;\n      line-height: 1.2;\n    }\n\n    #hns-phishing-landing .intro__label::before {\n      content: \"\";\n      width: 7px;\n      height: 7px;\n      border-radius: 50%;\n      background: var(--accent);\n    }\n\n    #hns-phishing-landing .intro__copy {\n      max-width: 820px;\n      margin: 28px auto 0;\n      font-size: 25px;\n      line-height: 1.4;\n      text-wrap: pretty;\n    }\n\n    \/* ---------- Abschnitte ---------- *\/\n\n    #hns-phishing-landing .section {\n      padding: 110px 0 0;\n    }\n\n    #hns-phishing-landing .section__head {\n      max-width: 760px;\n      margin-bottom: 36px;\n    }\n\n    #hns-phishing-landing .section h2 {\n      margin: 16px 0 0;\n      font-size: 45px;\n      font-weight: 500;\n      line-height: 1.1;\n      text-wrap: balance;\n    }\n\n    #hns-phishing-landing .section__lead {\n      margin: 18px 0 0;\n      font-size: 18px;\n      color: var(--ink-muted);\n    }\n\n    \/* Aktuelle Meldung: Mint-Verlauf wie die Inhaltsfl\u00e4chen der Website *\/\n    #hns-phishing-landing .current {\n      display: grid;\n      grid-template-columns: 220px minmax(0, 1fr);\n      gap: 40px;\n      padding: 50px;\n      border-radius: 30px;\n      background: var(--status-gradient);\n    }\n\n    #hns-phishing-landing .current__meta {\n      font-size: 14px;\n      color: var(--ink-muted);\n    }\n\n    #hns-phishing-landing .current__date {\n      display: block;\n      margin-bottom: 4px;\n      font-size: 22px;\n      font-weight: 500;\n      line-height: 1.2;\n      color: var(--ink);\n    }\n\n    #hns-phishing-landing .current h3 {\n      margin: 0 0 20px;\n      font-size: 30px;\n      font-weight: 500;\n      line-height: 1.2;\n    }\n\n    #hns-phishing-landing .current p {\n      margin: 0 0 14px;\n      max-width: 720px;\n    }\n\n    #hns-phishing-landing .current p:last-child {\n      margin-bottom: 0;\n    }\n\n    #hns-phishing-landing .fact {\n      margin: 22px 0;\n      padding: 18px 22px;\n      border-radius: 18px;\n      background: var(--white);\n      max-width: 720px;\n    }\n\n    #hns-phishing-landing .fact strong {\n      display: block;\n      margin-bottom: 2px;\n      font-size: 13px;\n      font-weight: 500;\n      letter-spacing: 0.02em;\n      text-transform: uppercase;\n      color: var(--ink-muted);\n    }\n\n    #hns-phishing-landing .card {\n      padding: 44px;\n      border-radius: 30px;\n      background: var(--white);\n    }\n\n    #hns-phishing-landing .card h2 {\n      margin: 16px 0 20px;\n      font-size: 32px;\n    }\n\n    #hns-phishing-landing .card p {\n      margin: 0 0 14px;\n    }\n\n    \/* Karte \u201eF\u00fcr Hotels\u201c: drei Handlungspunkte nebeneinander, Trennlinien wie bei den Ma\u00dfnahmen. *\/\n    #hns-phishing-landing .steps {\n      display: grid;\n      grid-template-columns: repeat(3, minmax(0, 1fr));\n      gap: 36px;\n      margin: 30px 0 0;\n      padding: 0;\n      list-style: none;\n      counter-reset: step;\n    }\n\n    #hns-phishing-landing .steps li {\n      padding-top: 20px;\n      border-top: 1px solid var(--line);\n      counter-increment: step;\n    }\n\n    #hns-phishing-landing .steps li::before {\n      content: counter(step);\n      display: inline-grid;\n      place-items: center;\n      width: 28px;\n      height: 28px;\n      margin-bottom: 14px;\n      border-radius: 50%;\n      background: var(--mint);\n      font-size: 13px;\n    }\n\n    #hns-phishing-landing .steps h3,\n    #massnahmen h3 {\n      margin: 0 0 8px;\n      font-size: 20px;\n      font-weight: 500;\n      line-height: 1.3;\n    }\n\n    #hns-phishing-landing .steps p {\n      margin: 0;\n    }\n\n    \/* \u201eF\u00fcr Hotels\u201c und \u201eMa\u00dfnahmen\u201c nebeneinander; Hotels breiter, weil mehr Text \u2013 so enden beide\n   Karten etwa gleich hoch. *\/\n    #hns-phishing-landing .pair {\n      display: grid;\n      grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);\n      gap: 30px;\n    }\n\n    \/* Schritte untereinander, f\u00fcr die halbbreite Karte \u201eF\u00fcr Hotels\u201c: Nummer links neben dem Schritt,\n   wie die H\u00e4kchen bei den Ma\u00dfnahmen. *\/\n    #hns-phishing-landing .steps--stacked {\n      grid-template-columns: minmax(0, 1fr);\n      gap: 20px;\n      margin-top: 24px;\n    }\n\n    \/* Keine Linie unter der \u00dcberschrift, nur zwischen den Schritten *\/\n    #hns-phishing-landing .steps--stacked li:first-child {\n      padding-top: 0;\n      border-top: 0;\n    }\n\n    #hns-phishing-landing .steps--stacked li {\n      display: grid;\n      grid-template-columns: 28px minmax(0, 1fr);\n      column-gap: 14px;\n    }\n\n    #hns-phishing-landing .steps--stacked li::before {\n      grid-row: span 2;\n      margin: 0;\n    }\n\n    \/* HNS-Status (\u201eWas wir unternehmen\u201c) im Mint-Verlauf der aktuellen Meldung; die Hotel-Karte bleibt\n   wei\u00df und damit der st\u00e4rkere Kasten. H\u00e4kchen auf Wei\u00df, damit sie auf Mint sichtbar bleiben. *\/\n    #hns-phishing-landing .card--status {\n      background: var(--status-gradient);\n    }\n\n    #hns-phishing-landing .card--status .checks li::before {\n      background-color: var(--white);\n    }\n\n    \/* Links im Flie\u00dftext: unauff\u00e4llig, nur d\u00fcnn unterstrichen *\/\n    #hns-phishing-landing [data-guest-comms-link] {\n      color: inherit;\n      text-decoration: underline;\n      text-decoration-thickness: 1px;\n      text-underline-offset: 3px;\n    }\n\n    #hns-phishing-landing [data-guest-comms-link]:hover {\n      text-decoration-thickness: 2px;\n    }\n\n    #hns-phishing-landing [hidden] {\n      display: none !important;\n    }\n\n    \/* Keine Linie unter der \u00dcberschrift; gleicher Abstand zur \u00dcberschrift wie bei den Hotel-Schritten *\/\n    #hns-phishing-landing .checks {\n      margin: 24px 0 0;\n      padding: 0;\n      list-style: none;\n    }\n\n    #hns-phishing-landing .checks li:first-child {\n      padding-top: 0;\n    }\n\n    #hns-phishing-landing .checks li:first-child::before {\n      top: 1px;\n    }\n\n    #hns-phishing-landing .checks li {\n      position: relative;\n      padding: 14px 0 14px 40px;\n      border-bottom: 1px solid var(--line);\n    }\n\n    #hns-phishing-landing .checks li:last-child {\n      border-bottom: 0;\n    }\n\n    #hns-phishing-landing .checks li::before {\n      content: \"\";\n      position: absolute;\n      left: 0;\n      top: 15px;\n      width: 24px;\n      height: 24px;\n      border-radius: 50%;\n      background: var(--mint)\n        url(\"data:image\/svg+xml,%3Csvg xmlns='http:\/\/www.w3.org\/2000\/svg' viewBox='0 0 24 24'%3E%3Cpath d='M7 12.5l3.2 3.2L17 9' fill='none' stroke='%23000e07' stroke-width='1.8' stroke-linecap='round' stroke-linejoin='round'\/%3E%3C\/svg%3E\")\n        center \/ 20px no-repeat;\n    }\n\n    \/* ---------- FAQ (Aufklappen) ---------- *\/\n\n    #hns-phishing-landing .faq {\n      border-radius: 30px;\n      background: var(--white);\n      padding: 10px 44px;\n    }\n\n    #hns-phishing-landing .faq details {\n      border-bottom: 1px solid var(--line);\n    }\n\n    #hns-phishing-landing .faq details:last-child {\n      border-bottom: 0;\n    }\n\n    #hns-phishing-landing .faq summary,\n    #hns-phishing-landing .archive summary {\n      display: flex;\n      align-items: center;\n      gap: 20px;\n      list-style: none;\n      cursor: pointer;\n    }\n\n    #hns-phishing-landing .faq summary::-webkit-details-marker,\n    #hns-phishing-landing .archive summary::-webkit-details-marker {\n      display: none;\n    }\n\n    #hns-phishing-landing .faq summary {\n      justify-content: space-between;\n      padding: 26px 0;\n      font-size: 20px;\n      font-weight: 500;\n      line-height: 1.3;\n    }\n\n    #hns-phishing-landing .toggle {\n      position: relative;\n      flex: 0 0 auto;\n      width: 36px;\n      height: 36px;\n      border: 1px solid var(--ink);\n      border-radius: 50%;\n      transition: background-color 0.15s;\n    }\n\n    #hns-phishing-landing .toggle::before,\n    #hns-phishing-landing .toggle::after {\n      content: \"\";\n      position: absolute;\n      top: 50%;\n      left: 50%;\n      width: 12px;\n      height: 1.5px;\n      background: currentColor;\n      transform: translate(-50%, -50%);\n      transition: transform 0.2s;\n    }\n\n    #hns-phishing-landing .toggle::after {\n      transform: translate(-50%, -50%) rotate(90deg);\n    }\n\n    #hns-phishing-landing details[open] > summary .toggle {\n      background: var(--ink);\n      color: var(--white);\n    }\n\n    #hns-phishing-landing details[open] > summary .toggle::after {\n      transform: translate(-50%, -50%) rotate(0deg);\n    }\n\n    #hns-phishing-landing summary:hover .toggle {\n      background: var(--panel);\n    }\n\n    #hns-phishing-landing details[open] > summary:hover .toggle {\n      background: var(--ink);\n    }\n\n    \/* Zielgruppe nur bei eindeutig zielgruppenspezifischen Fragen: kleine graue Zeile \u00fcber der Frage. *\/\n    #hns-phishing-landing .faq__audience {\n      display: block;\n      margin-bottom: 4px;\n      font-size: 13px;\n      font-weight: 400;\n      line-height: 1.3;\n      color: var(--ink-muted);\n    }\n\n    #hns-phishing-landing .faq__answer {\n      max-width: 820px;\n      padding: 0 56px 28px 0;\n    }\n\n    #hns-phishing-landing .faq__answer p,\n    #hns-phishing-landing .faq__answer ul {\n      margin: 0 0 12px;\n    }\n\n    #hns-phishing-landing .faq__answer ul {\n      padding-left: 22px;\n    }\n\n    #hns-phishing-landing .faq__answer li {\n      margin-bottom: 4px;\n    }\n\n    \/* ---------- Bisherige Updates ---------- *\/\n\n    #hns-phishing-landing .archive__note {\n      margin: 0 0 28px;\n      padding: 20px 24px;\n      border-radius: 18px;\n      background: var(--white);\n      font-size: 15px;\n      color: var(--ink-muted);\n      max-width: 820px;\n    }\n\n    #hns-phishing-landing .archive__note p {\n      margin: 0;\n    }\n\n    #hns-phishing-landing .archive__note p + p {\n      margin-top: 6px;\n      color: var(--ink);\n    }\n\n    #hns-phishing-landing .archive {\n      margin: 0;\n      padding: 0;\n      list-style: none;\n      border-top: 1px solid var(--line);\n    }\n\n    #hns-phishing-landing .archive > li {\n      border-bottom: 1px solid var(--line);\n    }\n\n    #hns-phishing-landing .archive summary {\n      padding: 22px 0;\n    }\n\n    \/* Archiv: Inhalt und Struktur kommen unver\u00e4ndert aus archiv\/meldungen.json (Originalseite). Hier nur\n   Darstellung \u2013 keine Regel darf Text einf\u00fcgen, umformen oder ausblenden. *\/\n    #hns-phishing-landing .archive__stand {\n      flex: 1;\n      font-size: 20px;\n      font-weight: 500;\n      line-height: 1.3;\n      font-variant-numeric: tabular-nums;\n    }\n\n    #hns-phishing-landing .archive__body {\n      margin: 0 0 28px;\n      padding: 36px 44px;\n      border-radius: 24px;\n      background: var(--white);\n      font-size: 16px;\n      max-width: 860px;\n    }\n\n    \/* \u00dcberschriftenebenen wie im Original: H2 gr\u00f6\u00dfer als H4 *\/\n    #hns-phishing-landing .archive__body h2 {\n      margin: 28px 0 10px;\n      font-size: 21px;\n      font-weight: 500;\n      line-height: 1.3;\n    }\n\n    #hns-phishing-landing .archive__body h4 {\n      margin: 24px 0 8px;\n      font-size: 17px;\n      font-weight: 500;\n      line-height: 1.3;\n    }\n\n    #hns-phishing-landing .archive__body > :first-child {\n      margin-top: 0;\n    }\n\n    #hns-phishing-landing .archive__body strong {\n      font-weight: 700;\n    }\n\n    #hns-phishing-landing .archive__body p,\n    #hns-phishing-landing .archive__body ul,\n    #hns-phishing-landing .archive__body ol {\n      margin: 0 0 12px;\n    }\n\n    #hns-phishing-landing .archive__body ul,\n    #hns-phishing-landing .archive__body ol {\n      padding-left: 22px;\n    }\n\n    \/* Die Archivliste selbst ist eine <ol>; ohne diese Regel zeigt der Browser Kreise wie bei\n   verschachtelten Listen. *\/\n    #hns-phishing-landing .archive__body ul {\n      list-style: disc;\n    }\n\n    \/* Im Original stehen manche Listenpunkte in je eigener Liste \u2013 optisch als eine Liste zeigen. *\/\n    #hns-phishing-landing .archive__body ul + ul {\n      margin-top: -8px;\n    }\n\n    #hns-phishing-landing .archive__body li {\n      margin-bottom: 4px;\n    }\n\n    \/* ---------- Kontakt ---------- *\/\n\n    \/* ---------- Abschluss (Kontakt) ---------- *\/\n\n    .closing {\n      padding-bottom: 80px;\n      text-align: center;\n    }\n\n    .closing h2 {\n      max-width: 700px;\n      margin: 0 auto;\n    }\n\n    .closing__text {\n      max-width: 700px;\n      margin: 20px auto 0;\n      font-size: 25px;\n      line-height: 1.3;\n      text-wrap: pretty;\n    }\n\n    .closing__ways {\n      display: flex;\n      flex-direction: column;\n      align-items: center;\n      gap: 21px;\n      margin-top: 34px;\n    }\n\n    .closing__button {\n      display: inline-block;\n      padding: 9px 15px 8px;\n      border: 1px solid var(--ink) !important;\n      border-radius: 40px;\n      font-size: 12px;\n      line-height: 1.2;\n      text-decoration: none;\n      transition:\n        background-color 0.15s,\n        color 0.15s;\n    }\n\n    .closing__button:hover {\n      background: var(--ink) !important;\n      color: var(--white) !important;\n    }\n\n    .closing__hours {\n      margin: 24px 0 0;\n      font-size: 14px;\n      color: var(--ink-muted) !;\n    }\n\n    #kontakt-title {\n      margin: 16px auto 0 !important;\n    }\n\n    @media (max-width: 700px) {\n      .section {\n        padding-top: 72px;\n      }\n\n      .section h2 {\n        font-size: 32px;\n      }\n\n      .closing {\n        padding-bottom: 60px;\n      }\n\n      .section.closing h2 {\n        font-size: 28px;\n        line-height: 1.2;\n      }\n\n      .closing__text {\n        font-size: 20px;\n      }\n    }\n\n    \/* ---------- Fu\u00df ---------- *\/\n\n    #hns-phishing-landing .site-footer {\n      margin-top: 120px;\n      padding: 60px 0 50px;\n      background: var(--ink);\n      color: rgba(255, 255, 255, 0.72);\n      font-size: 14px;\n    }\n\n    #hns-phishing-landing .site-footer .wrap {\n      display: flex;\n      flex-wrap: wrap;\n      align-items: flex-end;\n      justify-content: space-between;\n      gap: 24px;\n    }\n\n    #hns-phishing-landing .site-footer .logo {\n      color: var(--white);\n      font-size: 26px;\n    }\n\n    #hns-phishing-landing .site-footer nav {\n      display: flex;\n      flex-wrap: wrap;\n      gap: 22px;\n    }\n\n    \/* ---------- Banner auf der Startseite (banner.html) ---------- *\/\n\n    #hns-phishing-landing .home-banner {\n      background: var(--ink);\n      color: var(--white);\n      font-size: 14px;\n    }\n\n    #hns-phishing-landing .home-banner .wrap {\n      display: flex;\n      align-items: center;\n      justify-content: center;\n      gap: 14px;\n      min-height: 46px;\n      padding-top: 8px;\n      padding-bottom: 8px;\n      text-align: center;\n    }\n\n    #hns-phishing-landing .home-banner__dot {\n      flex: 0 0 auto;\n      width: 8px;\n      height: 8px;\n      border-radius: 50%;\n      background: var(--accent);\n    }\n\n    #hns-phishing-landing .home-banner a {\n      display: inline-flex;\n      align-items: center;\n      gap: 6px;\n      padding: 4px 12px;\n      border: 1px solid rgba(255, 255, 255, 0.6);\n      border-radius: 20px;\n      font-size: 13px;\n      text-decoration: none;\n      white-space: nowrap;\n    }\n\n    #hns-phishing-landing .home-banner a:hover {\n      background: var(--white);\n      color: var(--ink);\n    }\n\n    #hns-phishing-landing .demo-note {\n      margin: 60px auto 0;\n      max-width: 640px;\n      padding: 0 24px;\n      text-align: center;\n      color: var(--ink-muted);\n      font-size: 15px;\n    }\n\n    #hns-phishing-landing .demo-stage {\n      display: grid;\n      place-items: center;\n      min-height: 420px;\n      margin-top: 50px;\n      border-radius: 0 40px 0 0;\n      background: linear-gradient(135deg, #dfece4 0%, #f7f7f2 100%);\n      font-size: 56px;\n      font-weight: 500;\n      line-height: 1.02;\n      text-align: center;\n    }\n\n    \/* ---------- Schmale Bildschirme ---------- *\/\n\n    @media (max-width: 1100px) {\n      #hns-phishing-landing .site-nav > :not(.site-nav__cta) {\n        display: none;\n      }\n\n      #hns-phishing-landing .stage__inner {\n        grid-template-columns: minmax(0, 1fr);\n        gap: 0;\n      }\n\n      #hns-phishing-landing .stage__image {\n        height: 380px;\n        margin-right: 40px;\n        width: calc(100% - 40px);\n      }\n\n      #hns-phishing-landing .stage__text {\n        max-width: none;\n        padding: 40px 40px 56px;\n      }\n\n      #hns-phishing-landing .stage h1 {\n        font-size: 52px;\n      }\n\n      #hns-phishing-landing .intro {\n        padding-top: 80px;\n      }\n\n      #hns-phishing-landing .intro__copy {\n        font-size: 21px;\n      }\n\n      #hns-phishing-landing .pair,\n      #hns-phishing-landing .steps {\n        grid-template-columns: minmax(0, 1fr);\n      }\n\n      #hns-phishing-landing .steps {\n        gap: 24px;\n      }\n\n      #hns-phishing-landing .current {\n        grid-template-columns: minmax(0, 1fr);\n        gap: 16px;\n      }\n\n      #hns-phishing-landing .archive__body {\n        margin-left: 0;\n      }\n\n      #hns-phishing-landing .contact {\n        grid-template-columns: minmax(0, 1fr);\n      }\n    }\n\n    @media (max-width: 640px) {\n      #hns-phishing-landing {\n        font-size: 16px;\n      }\n\n      #hns-phishing-landing .wrap {\n        padding: 0 16px;\n      }\n\n      #hns-phishing-landing .site-header .wrap {\n        height: 70px;\n      }\n\n      #hns-phishing-landing .site-header__page {\n        display: none;\n      }\n\n      #hns-phishing-landing .site-lang {\n        margin-left: 8px;\n      }\n\n      #hns-phishing-landing .stage {\n        padding-top: 24px;\n      }\n\n      #hns-phishing-landing .stage__image {\n        height: 280px;\n        margin-right: 16px;\n        width: calc(100% - 16px);\n      }\n\n      #hns-phishing-landing .stage__text {\n        padding: 28px 16px 40px;\n      }\n\n      #hns-phishing-landing .stage h1 {\n        font-size: 38px;\n      }\n\n      #hns-phishing-landing .intro {\n        padding-top: 56px;\n      }\n\n      #hns-phishing-landing .intro__copy {\n        font-size: 19px;\n      }\n\n      #hns-phishing-landing .section {\n        padding-top: 72px;\n      }\n\n      #hns-phishing-landing .section h2 {\n        font-size: 32px;\n      }\n\n      #hns-phishing-landing .current,\n      #hns-phishing-landing .card,\n      #hns-phishing-landing .contact {\n        padding: 28px 22px;\n        border-radius: 24px;\n      }\n\n      #hns-phishing-landing .current h3 {\n        font-size: 24px;\n      }\n\n      #hns-phishing-landing .faq {\n        padding: 4px 20px;\n        border-radius: 24px;\n      }\n\n      #hns-phishing-landing .faq summary {\n        font-size: 17px;\n        padding: 20px 0;\n      }\n\n      #hns-phishing-landing .faq__answer {\n        padding-right: 0;\n      }\n\n      #hns-phishing-landing .archive__stand {\n        font-size: 17px;\n      }\n\n      #hns-phishing-landing .archive__body {\n        padding: 24px 20px;\n      }\n\n      #hns-phishing-landing .contact__ways {\n        min-width: 0;\n      }\n\n      #hns-phishing-landing .demo-stage {\n        font-size: 34px;\n      }\n    }\n\n    \/* Elementor\/WordPress isolation for this embedded fragment. *\/\n    #hns-phishing-landing {\n      width: 100%;\n    }\n    #hns-phishing-landing summary {\n      appearance: none;\n      -webkit-appearance: none;\n      margin: 0;\n      border: 0;\n      border-radius: 0;\n      background: transparent;\n      box-shadow: none;\n      color: inherit;\n      font: inherit;\n      text-transform: none;\n    }\n    #hns-phishing-landing details {\n      margin: 0;\n      padding: 0;\n    }\n  <\/style>\n  <div class=\"wrap\">\n    <!-- Aktuelle Meldung -->\n\n    <!-- F\u00fcr Hotels und Ma\u00dfnahmen nebeneinander. Der Generator steht im FAQ. -->\n    <div class=\"section pair\">\n      <section class=\"card\" id=\"hotels\" aria-labelledby=\"hotels-title\">\n        <span class=\"eyebrow\" data-i18n=\"hotels.eyebrow\">F\u00fcr Hotels<\/span>\n        <h2 id=\"hotels-title\" data-i18n=\"hotels.title\">\n          Was Sie jetzt tun k\u00f6nnen\n        <\/h2>\n\n        <ol class=\"steps steps--stacked\">\n          <li>\n            <h3 data-i18n=\"hotels.step1.title\">\n              Rezeption und Reservierung informieren\n            <\/h3>\n            <div class=\"steps__text\" data-i18n=\"hotels.step1.text\">\n                  <p>\n                    Weisen Sie darauf hin, dass auch Nachrichten mit korrekten Buchungsdaten betr\u00fcgerisch sein k\u00f6nnen. Das gilt\n                    vor der Anreise bei Check-in oder Zahlungen ebenso wie nach der Abreise bei angeblichen Nachzahlungen oder\n                    R\u00fcckerstattungen. Name, Reisezeitraum oder Buchungsnummer sind kein Echtheitsbeweis.\n                  <\/p>\n                <\/div>\n          <\/li>\n\n          <li>\n            <h3 data-i18n=\"hotels.step2.title\">\n              Eigene Kommunikationswege klar benennen\n            <\/h3>\n            <div class=\"steps__text\" data-i18n=\"hotels.step2.text\">\n              <p>\n                Halten Sie fest, welche Check-in-, Registrierungs- und\n                Zahlungsdienste Sie nutzen und \u00fcber welche Domains Sie mit\n                G\u00e4sten kommunizieren. Mit unserem\n                <a data-guest-comms-link>Text-Generator<\/a> erstellen Sie daraus\n                passende Hinweise.\n              <\/p>\n            <\/div>\n          <\/li>\n\n          <li>\n            <h3 data-i18n=\"hotels.step3.title\">Verdachtsf\u00e4lle sichern<\/h3>\n            <div class=\"steps__text\" data-i18n=\"hotels.step3.text\">\n              <p>\n                Bewahren Sie verd\u00e4chtige Nachrichten m\u00f6glichst im Original auf.\n                Sichern Sie Absender, Zeitpunkt, Links oder Domains und\n                Screenshots. Bei E-Mails m\u00f6glichst auch die Originalnachricht\n                mit Headern.\n              <\/p>\n            <\/div>\n          <\/li>\n\n          <li>\n            <h3 data-i18n=\"hotels.step4.title\">Verdachtsf\u00e4lle melden<\/h3>\n            <div class=\"steps__text\" data-i18n=\"hotels.step4.text\">\n                  <p>\n                    Melden Sie neue F\u00e4lle bitte an <strong>info@hotelnetsolutions.de<\/strong>. Hilfreich sind Angaben zum\n                    Hotel, zur betroffenen Buchung, zum Reisezeitraum und zum Zeitpunkt der Kontaktaufnahme.\n                  <\/p>\n                <\/div>\n          <\/li>\n        <\/ol>\n      <\/section>\n\n      <section\n        class=\"card card--status\"\n        id=\"massnahmen\"\n        aria-labelledby=\"massnahmen-title\"\n      >\n        <span class=\"eyebrow\" data-i18n=\"measures.eyebrow\">Ma\u00dfnahmen<\/span>\n        <h2 id=\"massnahmen-title\" data-i18n=\"measures.title\">\n          Was wir unternehmen\n        <\/h2>\n\n        <ul class=\"checks\">\n          <li data-i18n=\"measures.closed\">\n            <h3>Schwachstelle geschlossen<\/h3>\n            <p>\n              Die identifizierte Schwachstelle wurde am 19. September 2026\n              geschlossen.\n            <\/p>\n          <\/li>\n\n          <li data-i18n=\"measures.interfaces\">\n                <h3>Schnittstellen zus\u00e4tzlich abgesichert<\/h3>\n                <p>\n                  Authentifizierungs- und Zugriffsschutz an relevanten Schnittstellen sowie das Monitoring unserer Systeme\n                  wurden verst\u00e4rkt. Weitere PMS- und Datenschnittstellen werden gepr\u00fcft und weiter abgesichert.\n                <\/p>\n              <\/li>\n\n          <li data-i18n=\"measures.contacts\">\n            <h3>\u00dcbertragung von Kontaktdaten reduziert<\/h3>\n            <p>\n              Die \u00dcbertragung von E-Mail-Adressen und Telefonnummern an\n              angebundene Systeme wurde eingeschr\u00e4nkt; Kontaktdaten in\n              Best\u00e4tigungen werden st\u00e4rker maskiert.\n            <\/p>\n          <\/li>\n\n          <li data-i18n=\"measures.functions\">\n            <h3>Funktionen vorsorglich eingeschr\u00e4nkt<\/h3>\n            <p>\n              Einzelne Funktionen wurden vorsorglich deaktiviert, bis die\n              zugeh\u00f6rigen Zugriffswege abgesichert waren.\n            <\/p>\n          <\/li>\n\n          <li data-i18n=\"measures.review\">\n                <h3>Externer Cybersecurity-Spezialist ausgew\u00e4hlt<\/h3>\n                <p>\n                  Ein auf Cybersecurity und Incident Response spezialisiertes Unternehmen wurde ausgew\u00e4hlt. Der Umfang der\n                  unabh\u00e4ngigen Untersuchung und Sicherheitspr\u00fcfung wird derzeit abgestimmt.\n                <\/p>\n              <\/li>\n\n          <li data-i18n=\"measures.authorities\">\n                <h3>Landeskriminalamt informiert und neue F\u00e4lle analysiert<\/h3>\n                <p>\n                  Der Vorfall wurde dem Landeskriminalamt gemeldet. Neue Verdachtsf\u00e4lle flie\u00dfen in die laufende Analyse ein.\n                <\/p>\n              <\/li>\n        <\/ul>\n      <\/section>\n    <\/div>\n\n    <!-- H\u00e4ufige Fragen -->\n    <section class=\"section\" id=\"fragen\" aria-labelledby=\"fragen-title\">\n      <div class=\"section__head\">\n        <span class=\"eyebrow\">FAQ<\/span>\n        <h2 id=\"fragen-title\" data-i18n=\"faq.title\">H\u00e4ufige Fragen<\/h2>\n      <\/div>\n\n      <div class=\"faq\">\n        <details>\n          <summary>\n            <span data-i18n=\"faq.happened.q\">Was ist passiert?<\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.happened.a\">\n                <p>\n                  Bei HotelNetSolutions wurde eine technische Schwachstelle in einer Schnittstelle zwischen HotelControl und einem\n                  angebundenen Hotelsystem (PMS) ausgenutzt. Durch manipulierte Anfragen war es m\u00f6glich, Buchungsinformationen\n                  abzurufen, die \u00fcber den eigentlich vorgesehenen Umfang hinausgingen.\n                <\/p>\n                <p>\n                  Im Zusammenhang mit dem Vorfall werden solche Buchungsinformationen f\u00fcr sehr glaubw\u00fcrdig wirkende\n                  Phishingnachrichten an Hotelg\u00e4ste genutzt. Dabei geht es sowohl um Nachrichten vor der Anreise, etwa zu\n                  Check-in oder Zahlungen, als auch um E-Mails nach der Abreise, etwa zu angeblichen Nachzahlungen oder\n                  R\u00fcckerstattungen.\n                <\/p>\n              <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.data.q\"\n              >Welche Daten k\u00f6nnen betroffen sein?<\/span\n            >\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.data.a\">\n            <p>\n              Nach den bislang bekannten F\u00e4llen k\u00f6nnen insbesondere folgende\n              Buchungsinformationen betroffen sein:\n            <\/p>\n            <ul>\n              <li>Hotelname und Buchungsnummer<\/li>\n              <li>Name des Gastes<\/li>\n              <li>Kontaktdaten wie E-Mail-Adresse und Telefonnummer<\/li>\n              <li>An- und Abreisedatum<\/li>\n              <li>Gesamtbetrag der Buchung<\/li>\n            <\/ul>\n            <p>\n              Welche Angaben im Einzelfall betroffen waren, kann je nach Buchung\n              variieren.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.closed.q\"\n              >Ist die Schwachstelle geschlossen?<\/span\n            >\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.closed.a\">\n            <p>\n              Ja. Die identifizierte Schwachstelle wurde am 19. September 2026\n              geschlossen. Die weitere technische und organisatorische\n              Aufarbeitung l\u00e4uft.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.period.q\"\n              >Von welchem Zeitraum sprechen wir?<\/span\n            >\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.period.a\">\n            <p>\n              Beginn und vollst\u00e4ndiger Umfang des unberechtigten Zugriffs lassen\n              sich r\u00fcckwirkend derzeit nicht belastbar bestimmen.\n            <\/p>\n            <p>\n              Gemeldete Phishingf\u00e4lle beziehen sich auf Reservierungen aus einem\n              breiteren Zeitraum. Das Buchungs- oder Reisedatum einer\n              Reservierung ist jedoch nicht mit dem Zeitpunkt eines\n              unberechtigten Zugriffs gleichzusetzen.\n            <\/p>\n            <p>\n              Die zeitliche Rekonstruktion ist Teil der laufenden Aufarbeitung.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.ongoing.q\"\n              >Warum k\u00f6nnen weiterhin Phishingnachrichten auftauchen, obwohl die\n              Schwachstelle geschlossen ist?<\/span\n            >\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.ongoing.a\">\n                <p>\n                  Das Schlie\u00dfen der Schwachstelle verhindert weitere Zugriffe \u00fcber den identifizierten Angriffsweg. Informationen,\n                  die zuvor bereits unberechtigt abgerufen wurden, k\u00f6nnen jedoch weiterhin f\u00fcr Betrugsversuche verwendet werden.\n                <\/p>\n                <p>\n                  Das gilt auch nach einem Aufenthalt. Aktuell treten beispielsweise E-Mails zu angeblichen Nachzahlungen oder\n                  R\u00fcckerstattungen auf, die auf einen Link f\u00fchren. Solche Links sollten nicht ungepr\u00fcft ge\u00f6ffnet werden; im\n                  Zweifel sollte die Nachricht direkt beim Hotel \u00fcber bekannte Kontaktdaten gepr\u00fcft werden.\n                <\/p>\n              <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.payment.q\"\n              >Sind Kreditkarten- oder Zahlungsdaten abgeflossen?<\/span\n            >\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.payment.a\">\n            <p>\n              Nach aktuellem Kenntnisstand liegen keine Hinweise darauf vor,\n              dass Kreditkarten- oder sonstige Zahlungsdaten \u00fcber die\n              identifizierte Schwachstelle bei HotelNetSolutions abgeflossen\n              sind.\n            <\/p>\n            <p>\n              Davon zu unterscheiden sind Zahlungs- oder Zugangsdaten, die ein\n              Gast anschlie\u00dfend selbst auf einer betr\u00fcgerischen Website\n              eingegeben hat.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.q4\">\n              <span class=\"faq__audience\">F\u00fcr G\u00e4ste<\/span>Ich habe eine\n              verd\u00e4chtige Nachricht erhalten. Was soll ich tun?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\">\n            <p data-i18n=\"faq.a4\">\n              \u00d6ffnen Sie im Zweifel keine enthaltenen Links und nehmen Sie\n              dar\u00fcber keine Zahlung vor. Pr\u00fcfen Sie die Nachricht direkt beim\n              Hotel \u00fcber einen Ihnen bekannten Kontaktweg, beispielsweise die\n              offizielle Website oder Telefonnummer.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.q5\">\n              <span class=\"faq__audience\">F\u00fcr G\u00e4ste<\/span>Woran erkenne ich, ob\n              eine Nachricht wirklich von meinem Hotel stammt?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\">\n            <p data-i18n=\"faq.a5\">\n              Leider nicht immer zuverl\u00e4ssig. Auch korrekte Angaben wie Name,\n              Reisezeitraum oder Buchungsnummer sind kein Echtheitsbeweis.\n              Pr\u00fcfen Sie insbesondere, ob der verwendete Dienst und die\n              Internetadresse tats\u00e4chlich zu Ihrem Hotel geh\u00f6ren.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.q6\">\n              <span class=\"faq__audience\">F\u00fcr G\u00e4ste<\/span>Ich habe bereits Daten\n              eingegeben oder bezahlt. Was soll ich tun?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\">\n            <p data-i18n=\"faq.a6\">\n              Bei eingegebenen Zugangsdaten sollten Sie das betroffene Passwort\n              \u00fcber die offizielle Website oder App \u00e4ndern. Haben Sie Bank- oder\n              Kreditkartendaten eingegeben oder bereits bezahlt, kontaktieren\n              Sie bitte unverz\u00fcglich Ihre Bank, Ihren Kartenanbieter oder den\n              verwendeten Zahlungsdienstleister.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.pms.q\">\n              <span class=\"faq__audience\">F\u00fcr Hotels<\/span>Sind die angebundenen\n              PMS-Systeme ebenfalls betroffen?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\" data-i18n=\"faq.pms.a\">\n            <p>\n              Die von uns identifizierte Schwachstelle lag in einer\n              <strong\n                >Schnittstelle zwischen HotelControl und einem angebundenen\n                Hotelsystem (PMS)<\/strong\n              >. \u00dcber diese Schnittstelle konnten durch manipulierte Anfragen\n              Buchungsdaten \u00fcber den eigentlich vorgesehenen Umfang hinaus\n              abgerufen werden.\n            <\/p>\n            <p>\n              <strong\n                >Hinweise auf eine Schwachstelle in den angebundenen\n                PMS-Systemen selbst liegen uns nach aktuellem Kenntnisstand\n                nicht vor.<\/strong\n              >\n              F\u00fcr unsere Kunden besteht daher derzeit kein Handlungsbedarf\n              gegen\u00fcber ihrem PMS-Anbieter.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.q7\">\n              <span class=\"faq__audience\">F\u00fcr Hotels<\/span>Wie k\u00f6nnen wir unsere\n              G\u00e4ste informieren?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\">\n            <p data-i18n=\"faq.a7\">\n              HotelNetSolutions stellt Hotelkunden einen\n              <a data-guest-comms-link>Kommunikationsgenerator<\/a> zur\n              Verf\u00fcgung. Damit k\u00f6nnen Sie eine G\u00e4stemeldung, ein G\u00e4ste-FAQ und\n              ein FAQ f\u00fcr Rezeption und Reservierung erstellen \u2013 angepasst an\n              die tats\u00e4chlich von Ihrem Hotel verwendeten Check-in-,\n              Registrierungs- und Zahlungsdienste.\n            <\/p>\n          <\/div>\n        <\/details>\n\n        <details>\n          <summary>\n            <span data-i18n=\"faq.q8\">\n              <span class=\"faq__audience\">F\u00fcr Hotels<\/span>Wie melden wir einen\n              neuen Verdachtsfall?\n            <\/span>\n            <span class=\"toggle\" aria-hidden=\"true\"><\/span>\n          <\/summary>\n\n          <div class=\"faq__answer\">\n            <p data-i18n=\"faq.a8\">\n                  Neue Verdachtsf\u00e4lle melden Sie bitte an\n                  <a href=\"mailto:info@hotelnetsolutions.de\">info@hotelnetsolutions.de<\/a>. Bewahren Sie\n                  m\u00f6glichst die Originalnachricht, Absender bzw. Telefonnummer, Zeitpunkt sowie die verwendete URL oder Domain\n                  auf.\n                <\/p>\n          <\/div>\n        <\/details>\n      <\/div>\n    <\/section>\n\n    <!-- Bisherige Updates -->\n    <section class=\"section\" id=\"updates\" aria-labelledby=\"updates-title\">\n      <div class=\"section__head\">\n        <span class=\"eyebrow\" data-i18n=\"archive.eyebrow\">Archiv<\/span>\n        <h2 id=\"updates-title\" data-i18n=\"archive.title\">Bisherige Updates<\/h2>\n      <\/div>\n\n      <!-- Hinweis au\u00dferhalb des gesicherten Archivbereichs; auf Englisch mit der Kennzeichnung,\n               dass die Meldungen im deutschen Originalwortlaut stehen. -->\n      <div class=\"archive__note\">\n        <p data-i18n=\"archive.note1\">\n          Die folgenden Meldungen dokumentieren den jeweiligen damaligen\n          Kenntnisstand. Fr\u00fchere Einsch\u00e4tzungen wurden teilweise durch sp\u00e4tere\n          Erkenntnisse erg\u00e4nzt oder \u00fcberholt.\n        <\/p>\n        <p data-i18n=\"archive.note2\">\n          Ma\u00dfgeblich ist der aktuelle Stand oben auf dieser Seite.\n        <\/p>\n      <\/div>\n\n      <!-- Archivinhalt: Deutsch als Referenz; Englisch \u00fcber data-i18n. -->\n      <div lang=\"de\" data-i18n-attr=\"lang=archive.lang\">\n        <!-- ARCHIV:BEGINN \u00b7 erzeugt von scripts\/archiv.mjs aus archiv\/meldungen.json \u00b7 nicht von Hand bearbeiten -->\n        <ol class=\"archive\">\n          <li>\n            <details id=\"archiv-2026-09-25\">\n              <summary>\n                <span class=\"archive__stand\" data-i18n=\"archive.2026-09-25.stand\">Stand: 25.09.2026<\/span\n                ><span class=\"toggle\" aria-hidden=\"true\"><\/span>\n              <\/summary>\n              <div class=\"archive__body\" data-i18n=\"archive.2026-09-25.body\">\n                <h4>\n                  <strong>Aktueller Stand zu den Phishing Vorf\u00e4llen.<\/strong>\n                <\/h4>\n                <p>\n                  Hinweise auf eine Schwachstelle in den angebundenen\n                  PMS-Systemen liegen uns nicht vor. F\u00fcr unsere Kunden besteht\n                  daher nach aktuellem Kenntnisstand kein Handlungsbedarf\n                  gegen\u00fcber ihrem PMS-Anbieter.\n                <\/p>\n                <p>\n                  Der Zeitraum Oktober 2025 bis einschlie\u00dflich 19. September\n                  2026 bezeichnet den Zeitraum der Reservierungen, zu denen\n                  entsprechende Phishingf\u00e4lle gemeldet wurden. Dieser Zeitraum\n                  ist nicht mit der Dauer eines unberechtigten Zugriffs\n                  gleichzusetzen. F\u00fcr einen \u00fcber Monate andauernden Zugriff\n                  liegt uns kein entsprechender Nachweis vor.\n                <\/p>\n                <p>\n                  Einen exakten Zeitpunkt, ab dem die Schwachstelle erstmalig\n                  bestand beziehungsweise tats\u00e4chlich durch unberechtigte Dritte\n                  ausgenutzt wurde, k\u00f6nnen wir r\u00fcckwirkend nicht belastbar\n                  bestimmen.\n                <\/p>\n                <p>\n                  Im Rahmen der weiteren Log-Analyse haben wir inzwischen jedoch\n                  einen technischen Hinweis gefunden, der darauf schlie\u00dfen\n                  l\u00e4sst, dass sp\u00e4testens am 20.08.2026 ein Angriff auf die\n                  identifizierte Schwachstelle stattgefunden hat.\n                <\/p>\n              <\/div>\n            <\/details>\n          <\/li>\n          <li>\n            <details id=\"archiv-2026-09-21\">\n              <summary>\n                <span class=\"archive__stand\" data-i18n=\"archive.2026-09-21.stand\">Stand: 21.09.2026<\/span\n                ><span class=\"toggle\" aria-hidden=\"true\"><\/span>\n              <\/summary>\n              <div class=\"archive__body\" data-i18n=\"archive.2026-09-21.body\">\n                <h4><strong>Was ist passiert?<\/strong><\/h4>\n                <p>\n                  Am <strong>19.09.2026 gegen 14:00 Uhr<\/strong> konnten wir\n                  eine Schwachstelle in einer Schnittstelle zwischen\n                  HotelControl und einem angebundenen Hotelsystem (PMS)\n                  best\u00e4tigen und schlie\u00dfen.\n                <\/p>\n                <p>\n                  \u00dcber diese Schnittstelle war es durch manipulierte Anfragen\n                  m\u00f6glich, auf Buchungsdaten zuzugreifen, die \u00fcber die\n                  eigentlich vorgesehene Funktion hinausgingen.\n                <\/p>\n                <p>Nachweislich betroffen waren unter anderem:<\/p>\n                <ul>\n                  <li>Hotelname und Buchungsnummer<\/li>\n                  <li>Name und Kontaktdaten des Gastes<\/li>\n                  <li>An- und Abreisedatum<\/li>\n                  <li>Gesamtbetrag der Buchung<\/li>\n                  <li>Telefonnummer<\/li>\n                <\/ul>\n                <p>\n                  <br \/>Hinweise auf einen Abfluss von Kreditkarten- oder\n                  sonstigen Zahlungsdaten liegen uns weiterhin nicht vor.\n                <\/p>\n                <h4><strong>Welche Ma\u00dfnahmen haben wir ergriffen:<\/strong><\/h4>\n                <p>\n                  Die best\u00e4tigte Schwachstelle wurde unmittelbar geschlossen.\n                <\/p>\n                <p>\n                  Bereits zuvor und erg\u00e4nzend dazu haben wir zahlreiche\n                  Schutzma\u00dfnahmen umgesetzt, unter anderem:\n                <\/p>\n                <ul>\n                  <li>\n                    zus\u00e4tzliche Absicherung und Pr\u00fcfung von Schnittstellen,\n                  <\/li>\n                  <li>\n                    Einschr\u00e4nkung der \u00dcbertragung von E-Mail-Adressen und\n                    Telefonnummern an angebundene Systeme,\n                  <\/li>\n                  <li>\n                    zus\u00e4tzliche Authentifizierungs- und Zugriffsschutzma\u00dfnahmen,\n                  <\/li>\n                  <li>\n                    \u00dcberpr\u00fcfung weiterer PMS-Schnittstellen auf vergleichbare\n                    Schwachstellen,\n                  <\/li>\n                  <li>\n                    Maskierung von E-Mail-Adressen und Telefonnummern in k\u00fcnftig\n                    versendeten Best\u00e4tigungs-E-Mails,\n                  <\/li>\n                  <li>\n                    vor\u00fcbergehende Deaktivierung einzelner Funktionen, bis die\n                    zugeh\u00f6rigen Schnittstellen vollst\u00e4ndig abgesichert sind.\n                  <\/li>\n                <\/ul>\n                <p>\n                  Die vor\u00fcbergehend eingeschr\u00e4nkten Daten\u00fcbertragungen werden\n                  nach erfolgreicher Pr\u00fcfung und Absicherung schrittweise wieder\n                  freigegeben.<br \/>Unsere Systeme werden weiterhin intensiv auf\n                  ungew\u00f6hnliche Zugriffe und auff\u00e4llige Aktivit\u00e4ten \u00fcberwacht.\n                <\/p>\n                <h2>Bitte bleiben Sie weiterhin wachsam<\/h2>\n                <p>\n                  Besonders wichtig: Uns sind inzwischen auch vergleichbare\n                  Phishingf\u00e4lle bei Hotels bekannt, die nicht mit Systemen\n                  von&nbsp;HotelNetSolutions arbeiten.\n                <\/p>\n                <p>\n                  Die aktuell auftretenden Phishingangriffe beschr\u00e4nken sich\n                  daher offenbar nicht auf einen einzelnen Systemanbieter oder\n                  einen einzelnen technischen Angriffsweg.\n                <\/p>\n                <p>\n                  Bitte sensibilisieren Sie deshalb weiterhin Ihre\n                  Mitarbeitenden und G\u00e4ste.\n                <\/p>\n                <p>\n                  Hotelg\u00e4ste sollten insbesondere keine unerwarteten\n                  Zahlungsaufforderungen \u00fcber WhatsApp oder andere Messenger\n                  ungepr\u00fcft befolgen und keine Kreditkarten- oder Zahlungsdaten\n                  \u00fcber dort versendete Links eingeben.\n                <\/p>\n                <p>\n                  HotelNetSolutions fordert G\u00e4ste nicht per WhatsApp zur Eingabe\n                  oder Best\u00e4tigung von Kreditkarten- oder Zahlungsdaten auf.\n                <\/p>\n                <p>\n                  Mit der Identifizierung und Schlie\u00dfung der Schwachstelle am\n                  19.09.2026 konnte die technische Ursache des bei\n                  HotelNetSolutions festgestellten unberechtigten Zugriffs\n                  behoben werden. Die weitere Absicherung und \u00dcberwachung\n                  unserer Systeme hat weiterhin h\u00f6chste Priorit\u00e4t.\n                <\/p>\n              <\/div>\n            <\/details>\n          <\/li>\n          <li>\n            <details id=\"archiv-2026-09-18\">\n              <summary>\n                <span class=\"archive__stand\" data-i18n=\"archive.2026-09-18.stand\">Stand: 18.09.2026<\/span\n                ><span class=\"toggle\" aria-hidden=\"true\"><\/span>\n              <\/summary>\n              <div class=\"archive__body\" data-i18n=\"archive.2026-09-18.body\">\n                <h2>Aktueller Stand der Untersuchungen<\/h2>\n                <p>\n                  Die Zahl der gemeldeten F\u00e4lle nimmt weiter zu. Dabei zeigt\n                  sich inzwischen ein differenzierteres Bild:\n                <\/p>\n                <p>\n                  Uns werden sowohl Phishingf\u00e4lle gemeldet, bei denen die\n                  zugrunde liegenden Reservierungen \u00fcber unsere Systeme\n                  verarbeitet wurden, als auch F\u00e4lle, bei denen die den T\u00e4tern\n                  bekannten Reservierungsdaten nach unserer bisherigen Pr\u00fcfung\n                  nicht aus unseren Systemen stammen.\n                <\/p>\n                <p>\n                  Auch der Zeitraum der betroffenen Reservierungen hat sich\n                  erweitert. Nach aktuellem Stand werden uns Reservierungen aus\n                  dem Zeitraum Januar 2026 bis einschlie\u00dflich 13.09.2026\n                  gemeldet.\n                <\/p>\n                <p>\n                  Damit l\u00e4sst sich der zun\u00e4chst erkennbare Schwerpunkt auf einen\n                  eng begrenzten Buchungszeitraum nicht mehr best\u00e4tigen. Die\n                  unterschiedlichen Buchungszeitr\u00e4ume und die verschiedenen\n                  Quellen der Reservierungsdaten sind Gegenstand unserer\n                  weiterf\u00fchrenden Untersuchungen.\n                <\/p>\n                <h4><strong>Technische Untersuchungen<\/strong><\/h4>\n                <p>\n                  Wir haben die relevanten Systeme, Zugriffswege und\n                  Schnittstellen weitergehend untersucht.\n                <\/p>\n                <p>\n                  Nach dem derzeitigen Stand unserer technischen Pr\u00fcfungen gibt\n                  es keinen nachweisbaren Fremdzugriff auf die f\u00fcr die Buchungs-\n                  bzw. Kommunikationsprozesse verwendeten Logins oder\n                  Schnittstellen.\n                <\/p>\n                <p>\n                  Auch die Analyse der bei den relevanten Schnittstellen\n                  verwendeten IP-Adressen hat bislang keine Auff\u00e4lligkeiten\n                  ergeben, die auf einen unbefugten Zugriff hindeuten.\n                <\/p>\n                <p>\n                  Der in der vergangenen Nacht durchgef\u00fchrte externe\n                  ASV-Sicherheits-Scan wurde erfolgreich abgeschlossen. Im\n                  Rahmen dieses Scans wurden keine sicherheitsrelevanten\n                  Auff\u00e4lligkeiten festgestellt, die zu einem Nichtbestehen des\n                  Scans gef\u00fchrt h\u00e4tten.\n                <\/p>\n                <p>\n                  Diese Ergebnisse sind wichtige Erkenntnisse f\u00fcr unsere\n                  laufende Ursachenanalyse. Sie stellen jedoch keine\n                  abschlie\u00dfende Aussage \u00fcber die Ursache der Phishingvorf\u00e4lle\n                  dar. Die Untersuchungen der weiteren Datenfl\u00fcsse,\n                  Schnittstellen und beteiligten Systeme werden daher\n                  fortgef\u00fchrt.\n                <\/p>\n                <h4>\n                  <strong\n                    >Untersuchung der angebundenen Systeme und Partner<\/strong\n                  >\n                <\/h4>\n                <p>\n                  F\u00fcr die Verarbeitung von Gastdaten im Rahmen von\n                  OnePageBooking-Buchungen setzen wir keine weiteren\n                  Dienstleister f\u00fcr die Verarbeitung dieser Gastdaten ein.&nbsp;\n                <\/p>\n                <p>\n                  Gleichzeitig bestehen Schnittstellen zu externen Systemen und\n                  Partnern. Diese Schnittstellen und die damit verbundenen\n                  Datenfl\u00fcsse sind Bestandteil unserer laufenden\n                  Untersuchung.&nbsp;\n                <\/p>\n                <p>\n                  Wir stehen hierzu mit den betreffenden Partnern im engen\n                  Austausch. Auch unsere Partner haben die eingegangenen\n                  Meldungen zum Anlass genommen, ihre eigenen Systeme und\n                  Schnittstellen umfassend zu \u00fcberpr\u00fcfen.&nbsp;\n                <\/p>\n                <p>\n                  Im Rahmen dieser \u00dcberpr\u00fcfungen konnten bei einzelnen Partnern\n                  Schwachstellen identifiziert werden. Diese wurden durch die\n                  jeweiligen Partner nachgebessert bzw. behoben. Die daraus\n                  gewonnenen Erkenntnisse flie\u00dfen in unsere weitere\n                  Ursachenanalyse ein.\n                <\/p>\n                <h2>Bereits umgesetzte Schutzma\u00dfnahmen<\/h2>\n                <p>\n                  Unabh\u00e4ngig davon, ob einzelne technische Zugriffswege\n                  letztlich als Ursache f\u00fcr die gemeldeten Phishingf\u00e4lle\n                  best\u00e4tigt werden k\u00f6nnen, haben wir bereits zus\u00e4tzliche\n                  technische und organisatorische Ma\u00dfnahmen umgesetzt.&nbsp;\n                <\/p>\n                <p>Hierzu geh\u00f6ren unter anderem:&nbsp;<\/p>\n                <ul>\n                  <li>\n                    zus\u00e4tzliche Authentifizierungsmechanismen an relevanten\n                    Schnittstellen,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    die Deaktivierung bzw. Entfernung nicht mehr ben\u00f6tigter\n                    Schnittstellen,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    erweiterte Validierungen bei \u00c4nderungen von\n                    Buchungsdaten,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>zus\u00e4tzliche Zugriffsbeschr\u00e4nkungen,&nbsp;<\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    automatische Sperrmechanismen bei auff\u00e4lligen\n                    Zugriffsmustern,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    eine weitere Absicherung der Protel-Anbindung sowie&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    die Weiterentwicklung der entsprechenden Schnittstelle auf\n                    Basis einer modernen Token-basierten\n                    Authentifizierung.&nbsp;<br \/><br \/>\n                  <\/li>\n                <\/ul>\n                <p>\n                  Die bereits umgesetzten Ma\u00dfnahmen werden laufend \u00fcberpr\u00fcft und\n                  bei Bedarf erweitert.&nbsp;\n                <\/p>\n                <h2>\n                  Aktuell keine Hinweise auf einen Abfluss von Zahlungsdaten\n                <\/h2>\n                <p>\n                  Die uns gemeldeten Phishingnachrichten zielen darauf ab, G\u00e4ste\n                  unter Bezugnahme auf tats\u00e4chlich bestehende Reservierungen zur\n                  Eingabe von Zahlungs- bzw. Kreditkartendaten zu bewegen.&nbsp;\n                <\/p>\n                <p>\n                  Nach derzeitigem Kenntnisstand liegen uns keine Hinweise\n                  darauf vor, dass bei uns verarbeitete Kreditkarten- oder\n                  sonstige Zahlungsdaten abgeflossen sind.&nbsp;\n                <\/p>\n                <p>\n                  Der Umstand, dass einzelne G\u00e4ste nach einem solchen\n                  Phishingversuch tats\u00e4chlich einen finanziellen Schaden\n                  erlitten haben, bedeutet nicht, dass die dabei verwendeten\n                  Zahlungsdaten aus unseren Systemen stammen. Auch diese F\u00e4lle\n                  werden im Rahmen der laufenden Untersuchungen\n                  ber\u00fccksichtigt.&nbsp;\n                <\/p>\n                <h2>Erneute Zahlungsaufforderungen an G\u00e4ste<\/h2>\n                <p>\n                  Uns wurden inzwischen auch F\u00e4lle gemeldet, in denen G\u00e4ste\n                  erneut zur Zahlung ihrer bestehenden Reservierung aufgefordert\n                  wurden, obwohl die Reservierung bereits bestand bzw. die\n                  Zahlung teilweise noch nicht erfolgt war.&nbsp;\n                <\/p>\n                <p>\n                  Auch hierbei beziehen sich die T\u00e4ter auf konkrete\n                  Buchungsinformationen und versuchen, die G\u00e4ste dazu zu\n                  bewegen, Zahlungen \u00fcber einen von ihnen vorgegebenen Link bzw.\n                  Zahlungsweg vorzunehmen.&nbsp;\n                <\/p>\n                <p>\n                  Wir bitten unsere Kunden daher ausdr\u00fccklich, ihre G\u00e4ste \u00fcber\n                  die aktuell bekannten Phishingversuche zu informieren und f\u00fcr\n                  entsprechende Nachrichten zu sensibilisieren.&nbsp;\n                <\/p>\n                <h2>Bitte informieren Sie Ihre G\u00e4ste<\/h2>\n                <p>\n                  Bitte weisen Sie Ihre G\u00e4ste vorsorglich darauf hin, dass\n                  derzeit Phishingnachrichten im Zusammenhang mit\n                  Hotelreservierungen im Umlauf sind.&nbsp;\n                <\/p>\n                <p>\n                  HotelNetSolutions fordert G\u00e4ste nicht per WhatsApp dazu auf,\n                  eine bestehende Hotelreservierung durch Eingabe von\n                  Kreditkarten- oder Zahlungsdaten zu best\u00e4tigen.&nbsp;\n                <\/p>\n                <p>G\u00e4ste sollten daher:&nbsp;<\/p>\n                <ul>\n                  <li>\n                    keine Zahlungs- oder Kreditkartendaten aufgrund einer\n                    solchen Nachricht \u00fcbermitteln,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    keine Links in entsprechenden WhatsApp-Nachrichten\n                    \u00f6ffnen,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    keine Zahlungen \u00fcber dort angegebene Zahlungswege\n                    vornehmen,&nbsp;\n                  <\/li>\n                <\/ul>\n                <ul>\n                  <li>\n                    im Zweifel direkt das Hotel \u00fcber die bekannten offiziellen\n                    Kontaktdaten kontaktieren und die Echtheit einer\n                    Zahlungsaufforderung \u00fcberpr\u00fcfen.&nbsp;\n                  <\/li>\n                <\/ul>\n                <p>\n                  <br \/>Bitte weisen Sie Ihre G\u00e4ste insbesondere darauf hin,\n                  dass eine solche Nachricht nicht von Ihnen oder Ihren\n                  Dienstleistern stammt.&nbsp;\n                <\/p>\n                <p>\n                  Die Information und Sensibilisierung der G\u00e4ste ist aus unserer\n                  Sicht eine wichtige zus\u00e4tzliche Ma\u00dfnahme, um einen\n                  erfolgreichen Missbrauch der bereits bekannten\n                  Reservierungsinformationen zu verhindern.\n                <\/p>\n                <h2>Wie geht es weiter?<\/h2>\n                <p>\n                  Unsere technische Untersuchung l\u00e4uft mit hoher Priorit\u00e4t\n                  weiter. Wir pr\u00fcfen weiterhin m\u00f6gliche Zusammenh\u00e4nge zwischen\n                  den unterschiedlichen F\u00e4llen und untersuchen die Herkunft der\n                  den T\u00e4tern bekannten Reservierungsinformationen.&nbsp;\n                <\/p>\n                <p>\n                  Die bisherigen technischen Pr\u00fcfungen haben keinen\n                  nachweisbaren Fremdzugriff auf die untersuchten Logins oder\n                  relevanten Buchungs- und Kommunikationsschnittstellen ergeben.\n                  Gleichzeitig werden die Untersuchungen der angebundenen\n                  Systeme, Datenfl\u00fcsse und externen Schnittstellen\n                  fortgesetzt.&nbsp;\n                <\/p>\n                <p>\n                  Sollten sich neue belastbare Erkenntnisse insbesondere zur\n                  Ursache, zum Umfang, zu betroffenen Daten oder zu weiteren\n                  erforderlichen Schutzma\u00dfnahmen ergeben, werden wir unsere\n                  Kunden entsprechend informieren.&nbsp;\n                <\/p>\n                <p>\n                  Wir danken unseren Kunden f\u00fcr die zeitnahe Weitergabe weiterer\n                  Verdachtsf\u00e4lle und bitten weiterhin um Unterst\u00fctzung bei der\n                  Sensibilisierung ihrer G\u00e4ste.&nbsp;\n                <\/p>\n                <p>\n                  <strong\n                    >Wir bitten um Verst\u00e4ndnis, dass die Aufarbeitung des\n                    Vorfalls derzeit h\u00f6chste Priorit\u00e4t hat. Aufgrund der\n                    inzwischen sehr gro\u00dfen Zahl an Meldungen und Anfragen k\u00f6nnen\n                    wir nicht jeden einzelnen Fall unmittelbar individuell\n                    pr\u00fcfen und beantworten. Wir f\u00fchren die Informationen daher\n                    zun\u00e4chst zusammen und priorisieren die technische\n                    Gesamtanalyse, um m\u00f6gliche Zusammenh\u00e4nge und die Ursache\n                    schnellstm\u00f6glich belastbar zu ermitteln.<\/strong\n                  >&nbsp;\n                <\/p>\n              <\/div>\n            <\/details>\n          <\/li>\n          <li>\n            <details id=\"archiv-2026-09-16\">\n              <summary>\n                <span class=\"archive__stand\" data-i18n=\"archive.2026-09-16.stand\">Stand: 16.09.2026<\/span\n                ><span class=\"toggle\" aria-hidden=\"true\"><\/span>\n              <\/summary>\n              <div class=\"archive__body\" data-i18n=\"archive.2026-09-16.body\">\n                <p>\n                  Seit unserer letzten Information vom 11.09.2026 setzen wir die\n                  technische Untersuchung der gemeldeten Phishingvorf\u00e4lle mit\n                  hoher Priorit\u00e4t fort. Unser Ziel ist es weiterhin, die Ursache\n                  und m\u00f6gliche Zusammenh\u00e4nge entlang der beteiligten Systeme,\n                  Schnittstellen und Verarbeitungsschritte vollst\u00e4ndig\n                  aufzukl\u00e4ren und daraus erforderliche weitere Schutzma\u00dfnahmen\n                  abzuleiten.\n                <\/p>\n                <p>\n                  Die Untersuchungen sind zum jetzigen Zeitpunkt noch nicht\n                  abgeschlossen. Nach wie vor pr\u00fcfen wir insbesondere, auf\n                  welchem Weg die den unbekannten Dritten bekannten\n                  Reservierungsinformationen erlangt worden sein k\u00f6nnten und ob\n                  es einen gemeinsamen technischen Zusammenhang zwischen den\n                  bislang bekannten F\u00e4llen gibt.\n                <\/p>\n                <h2>Aktueller Stand<\/h2>\n                <p>\n                  Wir haben die relevanten technischen Schnittstellen und\n                  Zugriffswege weitergehend analysiert und dabei insbesondere\n                  diejenigen Endpunkte untersucht, \u00fcber die im Rahmen unserer\n                  Anwendungen und angebundenen Systeme personenbezogene Daten\n                  verarbeitet bzw. \u00fcbertragen werden.\n                <\/p>\n                <p>\n                  Hierbei arbeiten unsere Frontend- und Backend-Teams eng\n                  zusammen. In einem ersten Schritt wurden auf Seiten des\n                  Frontends die f\u00fcr die relevanten Anwendungen\n                  <strong>OPB5, OPB6 und VB3<\/strong> eingesetzten\n                  Schnittstellen erfasst und hinsichtlich der Verarbeitung\n                  personenbezogener Daten analysiert. Diese \u00dcbersicht wurde\n                  anschlie\u00dfend an unser Backend-Team \u00fcbergeben, um die\n                  entsprechenden Schnittstellen auch auf Backend-Seite\n                  vollst\u00e4ndig zu pr\u00fcfen.\n                <\/p>\n                <p>\n                  Die Untersuchung erfolgt damit \u00fcber die einzelnen\n                  Systemkomponenten hinweg. Auf Basis der Ergebnisse werden\n                  weitere technische Ma\u00dfnahmen umgesetzt bzw. gepr\u00fcft.\n                <\/p>\n                <p>\n                  <strong\n                    >Nach unserem derzeitigen Kenntnisstand sind von den bislang\n                    gemeldeten F\u00e4llen \u00fcberwiegend Reservierungen betroffen, die\n                    im Zeitraum vom 29.08.2026 bis einschlie\u00dflich 01.09.2026\n                    gebucht wurden.<\/strong\n                  >\n                  Vereinzelt liegen uns auch Meldungen zu Reservierungen\n                  au\u00dferhalb dieses Buchungszeitraums vor. Nach bisheriger\n                  Pr\u00fcfung handelt es sich hierbei jedoch um Reservierungen, die\n                  au\u00dferhalb unserer Systeme erfasst wurden. Die Untersuchungen\n                  hierzu dauern an.\n                <\/p>\n                <p>\n                  <strong\n                    >Zum jetzigen Zeitpunkt liegen uns weiterhin keine\n                    best\u00e4tigten Erkenntnisse \u00fcber eine Kompromittierung unserer\n                    Systeme oder einen erfolgreichen Angriff auf unsere Systeme\n                    vor.<\/strong\n                  >\n                  Aufgrund der noch laufenden Untersuchungen kann ein\n                  Zusammenhang mit einem m\u00f6glichen unbefugten Zugriff jedoch\n                  weiterhin nicht abschlie\u00dfend ausgeschlossen werden.\n                <\/p>\n                <h2>Bereits umgesetzte Sofortma\u00dfnahmen<\/h2>\n                <p>\n                  Unabh\u00e4ngig von der noch laufenden Ursachenanalyse haben wir\n                  bereits zus\u00e4tzliche technische Schutzma\u00dfnahmen umgesetzt, um\n                  die betreffenden Zugriffswege weiter abzusichern und das\n                  Risiko missbr\u00e4uchlicher Zugriffe zu reduzieren.\n                <\/p>\n                <p>Hierzu geh\u00f6ren unter anderem:<\/p>\n                <ul>\n                  <li>\n                    <strong>Zus\u00e4tzliche Authentifizierung:<\/strong> Bei\n                    relevanten Schnittstellen wurde eine zus\u00e4tzliche\n                    Authentifizierung eingef\u00fchrt.\n                  <\/li>\n                  <li>\n                    <strong\n                      >Deaktivierung nicht mehr ben\u00f6tigter\n                      Schnittstellen:<\/strong\n                    >\n                    Bestimmte Endpunkte wurden entfernt bzw. deaktiviert.\n                  <\/li>\n                  <li>\n                    <strong>Erweiterte Validierungen:<\/strong> Bei der \u00c4nderung\n                    von Buchungsdaten wird nun zus\u00e4tzlich gepr\u00fcft, ob die\n                    angegebene Buchungsgruppen-ID tats\u00e4chlich zu der zu\n                    \u00e4ndernden Buchung geh\u00f6rt.\n                  <\/li>\n                  <li>\n                    <strong>Zus\u00e4tzliche Zugriffsbeschr\u00e4nkungen:<\/strong> F\u00fcr\n                    einen bislang verwendeten Endpunkt zum\n                    Hotelverwaltungssystem Protel.\n                  <\/li>\n                  <li>\n                    <strong>Automatische Sperrmechanismen:<\/strong> Bei mehr als\n                    10 Anfragen innerhalb von zwei Minuten wird die betreffende\n                    IP-Adresse f\u00fcr eine Stunde blockiert. Bei wiederholten\n                    fehlerhaften Kombinationen aus Benutzername und Passwort\n                    erfolgt eine Sperrung der IP-Adresse f\u00fcr vier Stunden.\n                  <\/li>\n                  <li>\n                    <strong>Weiterentwicklung der Protel-Anbindung:<\/strong>\n                    Parallel arbeiten wir an einer neuen, auf JWT-Token\n                    basierenden Schnittstelle f\u00fcr die Protel-Anbindung, um die\n                    Authentifizierung und Absicherung der entsprechenden\n                    Zugriffe weiter zu verbessern.\n                  <\/li>\n                <\/ul>\n                <p>&nbsp;<\/p>\n                <p>\n                  Diese Ma\u00dfnahmen erfolgen vorsorglich und unabh\u00e4ngig davon, ob\n                  einzelne technische Zugriffswege letztlich als Ursache f\u00fcr die\n                  gemeldeten Phishingf\u00e4lle best\u00e4tigt werden k\u00f6nnen.\n                <\/p>\n                <h2>Weitere technische Untersuchungen<\/h2>\n                <p>\n                  Neben den bereits umgesetzten Sofortma\u00dfnahmen \u00fcberpr\u00fcfen wir\n                  weiterhin systematisch die Schnittstellen, \u00fcber die\n                  personenbezogene Daten verarbeitet oder \u00fcbertragen werden.\n                <\/p>\n                <p>Dabei betrachten wir insbesondere:<\/p>\n                <ul>\n                  <li>\n                    welche personenbezogenen Daten \u00fcber die jeweiligen\n                    Schnittstellen verarbeitet werden,\n                  <\/li>\n                  <li>\n                    welche Systeme und Komponenten an den jeweiligen\n                    Datenfl\u00fcssen beteiligt sind,\n                  <\/li>\n                  <li>\n                    welche Zugriffs- und Authentifizierungsmechanismen zum\n                    Einsatz kommen,\n                  <\/li>\n                  <li>\n                    welche externen bzw. angebundenen Systeme und Dienstleister\n                    in den jeweiligen Verarbeitungsschritten beteiligt sind und\n                  <\/li>\n                  <li>\n                    ob sich aus den bislang bekannten F\u00e4llen gemeinsame\n                    technische Zusammenh\u00e4nge ableiten lassen.\n                  <\/li>\n                <\/ul>\n                <p>&nbsp;<\/p>\n                <p>\n                  Die Ergebnisse dieser Analysen werden fortlaufend zwischen\n                  unseren Teams abgeglichen und bilden die Grundlage f\u00fcr weitere\n                  technische und organisatorische Ma\u00dfnahmen.\n                <\/p>\n                <h2>Was bedeutet das f\u00fcr Sie?<\/h2>\n                <p>\n                  Die bisherigen Empfehlungen aus unserer Information vom\n                  11.09.2026 bleiben unver\u00e4ndert bestehen.\n                <\/p>\n                <p>\n                  Bitte sensibilisieren Sie weiterhin Ihre Mitarbeitenden und\n                  insbesondere die f\u00fcr Reservierungen zust\u00e4ndigen Teams f\u00fcr das\n                  aktuell bekannte Angriffsmuster.\n                <\/p>\n                <p>\n                  <strong>Wichtig: Keine Zahlungsdaten per WhatsApp<\/strong>\n                <\/p>\n                <p>\n                  HotelNetSolutions fordert keine Kreditkarten- oder sonstigen\n                  Zahlungsdaten per WhatsApp zur Best\u00e4tigung einer bestehenden\n                  Reservierung an.\n                <\/p>\n                <p>\n                  Entsprechende Nachrichten sollten nicht beantwortet,\n                  enthaltene Links nicht ge\u00f6ffnet und keine Zahlungs- oder\n                  Kreditkartendaten \u00fcber die dort angegebenen Wege eingegeben\n                  werden.\n                <\/p>\n                <p>\n                  Sollten Sie weitere F\u00e4lle feststellen, bitten wir Sie\n                  weiterhin um eine m\u00f6glichst zeitnahe Meldung an uns. F\u00fcr die\n                  laufende Ursachenanalyse sind insbesondere das betroffene\n                  Hotel, Buchungsdatum und Buchungsweg, Anreise- und\n                  Abreisedatum, der Zeitpunkt der betr\u00fcgerischen Kontaktaufnahme\n                  sowie \u2013 soweit verf\u00fcgbar \u2013 Screenshots der erhaltenen\n                  Nachricht und die verwendete Absendernummer hilfreich.\n                <\/p>\n                <p>\n                  Bitte \u00fcbermitteln Sie dabei weiterhin nur die f\u00fcr die\n                  Untersuchung erforderlichen personenbezogenen Daten.\n                <\/p>\n                <h2>Wie geht es weiter?<\/h2>\n                <p>\n                  Unsere technische Untersuchung l\u00e4uft mit hoher Priorit\u00e4t\n                  weiter. Wir verfolgen weiterhin das Ziel, die Ursache der\n                  Vorf\u00e4lle und den m\u00f6glichen Weg der betroffenen\n                  Reservierungsinformationen vollst\u00e4ndig nachzuvollziehen.\n                <\/p>\n                <p>\n                  Parallel setzen wir zus\u00e4tzliche Schutzma\u00dfnahmen um und\n                  \u00fcberpr\u00fcfen weitere technische Zugriffswege, Schnittstellen und\n                  Datenfl\u00fcsse. Sollten sich aus den laufenden Untersuchungen\n                  neue belastbare Erkenntnisse insbesondere zur Ursache, zum\n                  Umfang, zu betroffenen Daten oder zu weiteren erforderlichen\n                  Schutzma\u00dfnahmen ergeben, werden wir Sie unverz\u00fcglich\n                  informieren.\n                <\/p>\n                <p>\n                  Wir danken Ihnen f\u00fcr Ihre Unterst\u00fctzung und die zeitnahe\n                  Weitergabe weiterer Verdachtsf\u00e4lle. Die Aufkl\u00e4rung der\n                  Vorf\u00e4lle und die weitere Absicherung unserer Systeme haben f\u00fcr\n                  uns weiterhin h\u00f6chste Priorit\u00e4t.\n                <\/p>\n                <p>Vielen Dank f\u00fcr Ihr Verst\u00e4ndnis und Ihre Unterst\u00fctzung.<\/p>\n              <\/div>\n            <\/details>\n          <\/li>\n          <li>\n            <details id=\"archiv-2026-09-11\">\n              <summary>\n                <span class=\"archive__stand\" data-i18n=\"archive.2026-09-11.stand\">Stand: 11.09.2026<\/span\n                ><span class=\"toggle\" aria-hidden=\"true\"><\/span>\n              <\/summary>\n              <div class=\"archive__body\" data-i18n=\"archive.2026-09-11.body\">\n                <p>\n                  Aktuell liegen uns mehrere Meldungen von Hotels zu\n                  gezielten&nbsp;Phishingvorf\u00e4llen gegen\u00fcber\n                  Hotelg\u00e4sten&nbsp;vor. Aufgrund der inzwischen vorliegenden\n                  Erkenntnisse m\u00f6chten wir Sie vorsorglich \u00fcber den aktuellen\n                  Sachstand und die von uns eingeleiteten Ma\u00dfnahmen informieren.\n                <\/p>\n                <p>\n                  Nach den bisherigen Meldungen werden G\u00e4ste von unbekannten\n                  Dritten \u00fcber WhatsApp unter Verwendung ausl\u00e4ndischer\n                  Telefonnummern kontaktiert und unter Bezugnahme auf\n                  tats\u00e4chlich bestehende Hotelreservierungen dazu aufgefordert,\n                  ihre Reservierung durch Angabe von Kreditkarten- oder\n                  Zahlungsdaten zu best\u00e4tigen.\n                <\/p>\n                <h2>Was ist passiert?<\/h2>\n                <p>\n                  Nach den bisherigen Meldungen werden G\u00e4ste von unbekannten\n                  Dritten \u00fcber WhatsApp unter Verwendung ausl\u00e4ndischer\n                  Telefonnummern kontaktiert und unter Bezugnahme auf\n                  tats\u00e4chlich bestehende Hotelreservierungen dazu aufgefordert,\n                  ihre Reservierung durch Angabe von Kreditkarten- oder\n                  Zahlungsdaten zu best\u00e4tigen.\n                <\/p>\n                <h2>Welche Informationen sind betroffen?<\/h2>\n                <p>\n                  Nach aktuellem Kenntnisstand verf\u00fcgen die handelnden Personen\n                  dabei zumindest \u00fcber konkrete Reservierungsinformationen,\n                  insbesondere den Namen des Gastes, den Namen des Hotels sowie\n                  das jeweilige Anreise- und Abreisedatum. In den bislang\n                  untersuchten F\u00e4llen bestehen zudem Auff\u00e4lligkeiten\n                  hinsichtlich des Buchungszeitpunkts, die derzeit n\u00e4her gepr\u00fcft\n                  werden.\n                <\/p>\n                <p>\n                  Woher diese Daten stammen und an welcher Stelle der\n                  Verarbeitungskette ein m\u00f6glicher unbefugter Zugriff oder\n                  Datenabfluss stattgefunden hat, pr\u00fcfen wir derzeit.\n                <\/p>\n                <h2>Was unternehmen wir?<\/h2>\n                <p>\n                  Seit Eingang der ersten Meldungen am 09.09.2026 untersuchen\n                  wir unsere Systeme sowie die relevanten Schnittstellen mit\n                  hoher Priorit\u00e4t auf m\u00f6gliche Schwachstellen, unberechtigte\n                  Zugriffe und sonstige verd\u00e4chtige Aktivit\u00e4ten. Hierzu geh\u00f6ren\n                  unter anderem die Auswertung relevanter Protokoll- und\n                  Zugriffsdaten sowie die Analyse von IP-Zugriffen. Parallel\n                  stehen wir hierzu mit unseren technischen Partnern und den\n                  relevanten an den Buchungsprozess angebundenen Dienstleistern\n                  im Austausch, um m\u00f6gliche Zusammenh\u00e4nge entlang der\n                  Verarbeitungskette zu identifizieren.\n                <\/p>\n                <p><strong>Aktueller Kenntnisstand<\/strong><\/p>\n                <p>\n                  Nach aktuellem Stand liegen uns keine best\u00e4tigten Erkenntnisse\n                  \u00fcber eine Kompromittierung unserer Systeme oder einen\n                  erfolgreichen Angriff auf unsere Systeme vor. Eine solche\n                  Kompromittierung kann zum jetzigen Zeitpunkt aufgrund der noch\n                  laufenden Untersuchungen jedoch auch nicht abschlie\u00dfend\n                  ausgeschlossen werden.\n                <\/p>\n                <p>\n                  F\u00fcr die weitere Ursachenanalyse ist insbesondere relevant,\n                  dass uns auch mindestens ein Fall bekannt ist, bei dem die f\u00fcr\n                  die Phishingnachricht verwendeten konkreten Reservierungsdaten\n                  nach unserem derzeitigen Kenntnisstand nicht in unseren\n                  Systemen vorlagen. Daher untersuchen wir derzeit insbesondere,\n                  welche weiteren Systeme, Schnittstellen, Dienstleister oder\n                  sonstigen Verarbeitungsschritte den bekannten F\u00e4llen gemeinsam\n                  sind. Die konkrete Ursache und Quelle des m\u00f6glichen\n                  Datenabflusses ist derzeit noch offen.\n                <\/p>\n                <h2>Hinweise f\u00fcr Hotels im Hinblick auf die DSGVO<\/h2>\n                <p>\n                  Da Sie als Hotel hinsichtlich der Daten Ihrer G\u00e4ste\n                  grunds\u00e4tzlich Verantwortlicher im Sinne der DSGVO sind, bitten\n                  wir Sie, den Sachverhalt auf Grundlage der Ihnen vorliegenden\n                  Informationen auch im Hinblick auf Ihre Pflichten nach Art. 33\n                  und gegebenenfalls Art. 34 DSGVO zu pr\u00fcfen. Soweit wir die\n                  betreffenden Daten als Auftragsverarbeiter f\u00fcr Sie\n                  verarbeiten, erfolgt diese Information zugleich vorsorglich im\n                  Hinblick auf unsere Informations- und Unterst\u00fctzungspflichten\n                  nach Art. 33 Abs. 2 DSGVO.<br \/><br \/>Bitte ber\u00fccksichtigen\n                  Sie bei Ihrer Risikobewertung insbesondere, dass die den\n                  unbekannten Dritten offenbar bekannten\n                  Reservierungsinformationen bereits gezielt eingesetzt werden,\n                  um G\u00e4ste zur Preisgabe von Kreditkarten- oder Zahlungsdaten zu\n                  bewegen. Nach unserem derzeitigen Kenntnisstand liegen\n                  hingegen keine Erkenntnisse vor, dass bei uns gespeicherte\n                  Kreditkarten- oder Zahlungsdaten Gegenstand eines m\u00f6glichen\n                  Datenabflusses sind.&nbsp;\n                <\/p>\n                <h2>Welche Ma\u00dfnahmen empfehlen wir?<\/h2>\n                <p>\n                  Unabh\u00e4ngig vom Ergebnis der laufenden Untersuchungen empfehlen\n                  wir vorsorglich, die Zugangsdaten der relevanten\n                  Benutzerkonten zu \u00fcberpr\u00fcfen und gegebenenfalls Passw\u00f6rter zu\n                  \u00e4ndern. Bitte verwenden Sie hierbei starke, einzigartige\n                  Passw\u00f6rter. Zudem sollten die eingesetzten Endger\u00e4te und\n                  angebundenen Systeme auf Aktualit\u00e4t und m\u00f6gliche\n                  Auff\u00e4lligkeiten \u00fcberpr\u00fcft werden.\n                <\/p>\n                <p>\n                  Wir empfehlen dar\u00fcber hinaus, Mitarbeitende mit G\u00e4stekontakt\n                  und insbesondere die f\u00fcr Reservierungen zust\u00e4ndigen Teams \u00fcber\n                  das aktuelle Angriffsmuster zu informieren.\n                <\/p>\n                <p>\n                  <strong>Wichtig: Keine Zahlungsdaten per WhatsApp<\/strong>\n                <\/p>\n                <p>\n                  Bitte weisen Sie Ihre Mitarbeitenden und betroffene G\u00e4ste\n                  au\u00dferdem darauf hin, dass HotelNetSolutions keine\n                  Kreditkarten- oder Zahlungsdaten per WhatsApp zur Best\u00e4tigung\n                  einer bestehenden Reservierung anfordert. Entsprechende\n                  Aufforderungen sollten nicht befolgt und in den Nachrichten\n                  enthaltene Links nicht ge\u00f6ffnet werden. G\u00e4ste, die\n                  entsprechende Nachrichten erhalten haben, sollten insbesondere\n                  keine Kreditkarten- oder sonstigen Zahlungsdaten aufgrund\n                  dieser Nachrichten oder \u00fcber darin enthaltene Links eingeben.\n                <\/p>\n                <p><strong>Was tun bei weiteren F\u00e4llen?<\/strong><\/p>\n                <p>\n                  Bitte teilen Sie uns weitere bekannt werdende F\u00e4lle m\u00f6glichst\n                  zeitnah mit. F\u00fcr die Ursachenanalyse sind insbesondere das\n                  betroffene Hotel, Buchungsdatum und Buchungsweg, Anreise- und\n                  Abreisedatum, Zeitpunkt der betr\u00fcgerischen Kontaktaufnahme\n                  sowie \u2013 soweit verf\u00fcgbar \u2013 Screenshots der erhaltenen\n                  Nachricht und die verwendete Absendernummer hilfreich. Bitte\n                  \u00fcbermitteln Sie dabei nur die f\u00fcr die Untersuchung\n                  erforderlichen personenbezogenen Daten.\n                <\/p>\n                <h2>Wie geht es weiter?<\/h2>\n                <p>\n                  Unsere technische Untersuchung l\u00e4uft mit hoher Priorit\u00e4t\n                  weiter. Sobald uns neue belastbare Erkenntnisse insbesondere\n                  zur Ursache, zum Umfang, zu den betroffenen Daten oder zu\n                  erforderlichen Schutzma\u00dfnahmen vorliegen, werden wir Sie\n                  unverz\u00fcglich informieren.\n                <\/p>\n                <p>\n                  Wir bedauern die hierdurch entstandenen Unannehmlichkeiten und\n                  versichern Ihnen, dass wir die Aufkl\u00e4rung der Vorf\u00e4lle mit\n                  hoher Priorit\u00e4t vorantreiben.\n                <\/p>\n                <p>\n                  Vielen Dank f\u00fcr Ihr Verst\u00e4ndnis und Ihre Unterst\u00fctzung.<br \/><br \/>Mit\n                  freundlichen Gr\u00fc\u00dfen<br \/>Sebastian D\u00fcpr\u00e9<br \/>\n                  Head of Operations\n                <\/p>\n              <\/div>\n            <\/details>\n          <\/li>\n        <\/ol>\n        <!-- ARCHIV:ENDE -->\n      <\/div>\n    <\/section>\n\n    <!-- Kontakt -->\n    <section\n      class=\"section closing\"\n      id=\"kontakt\"\n      aria-labelledby=\"kontakt-title\"\n    >\n      <h2 id=\"kontakt-title\" data-i18n=\"contact.title\">\n        Weitere Fragen oder Hinweise?\n      <\/h2>\n\n      <p class=\"closing__text\" data-i18n=\"contact.text\">\n        Wenn Sie eine verd\u00e4chtige Nachricht erhalten haben oder weitere\n        Informationen ben\u00f6tigen, erreichen Sie uns telefonisch oder per E-Mail.\n      <\/p>\n\n      <div class=\"closing__ways\">\n        <a class=\"closing__button\" href=\"tel:+4930770193000\">\n          +49 30 770 193 000\n        <\/a>\n\n        <a class=\"closing__button\" href=\"mailto:info@hotelnetsolutions.de\">\n          info@hotelnetsolutions.de\n        <\/a>\n      <\/div>\n\n      <p class=\"closing__hours\" data-i18n=\"contact.hours\">\n        Telefonisch Montag \u2013 Freitag, 9 \u2013 17 Uhr\n      <\/p>\n    <\/section>\n  <\/div>\n  <script>\n    (() => {\n      \"use strict\";\n      const root = document.getElementById(\"hns-phishing-landing\");\n      if (!root) return;\n\n      \/\/ Englische Fassung der Landingpage. Schl\u00fcssel wie data-i18n in index.html; Deutsch steht dort.\n      \/\/ N\u00fcchternes internationales Englisch. Aussagen nicht st\u00e4rker und nicht schw\u00e4cher als im Deutschen:\n      \/\/ \u201eabgeflossen\u201c \u2192 \u201eleaked\u201c, \u201ekeine Hinweise\u201c \u2192 \u201eno indication\u201c. Navigation wie auf\n      \/\/ hotelnetsolutions.de\/en\/. Das Archiv wird ebenfalls \u00fcber archive.* \u00fcbersetzt.\n\n      const TITLE = {\n        de: \"Phishing mit Buchungsdaten\",\n        en: \"Phishing using booking information\",\n      };\n\n      const EN = {\n        \"hotels.eyebrow\": \"For hotels\",\n        \"hotels.title\": \"What you can do now\",\n\n        \"hotels.step1.title\": \"Inform reception and reservations\",\n        \"hotels.step1.text\": `<p>Point out that even messages containing correct booking details can be fraudulent. This applies before arrival, for example in relation to check-in or payments, as well as after departure, for example regarding alleged additional charges or refunds. A guest\u2019s name, travel dates or booking number are not proof that a message is genuine.<\/p>`,\n\n        \"hotels.step2.title\": \"Make your official communication channels clear\",\n        \"hotels.step2.text\": `<p>Document which check-in, registration and payment services you use and which domains you use to communicate with guests. Our <a data-guest-comms-link>text generator<\/a> can create suitable guidance from this information.<\/p>`,\n\n        \"hotels.step3.title\": \"Preserve suspicious messages\",\n        \"hotels.step3.text\": `<p>Where possible, keep suspicious messages in their original form. Preserve the sender, time, links or domains and screenshots. For emails, keep the original message and headers wherever possible.<\/p>`,\n\n        \"hotels.step4.title\": \"Report suspicious cases\",\n        \"hotels.step4.text\": `<p>Please report new cases to <strong>info@hotelnetsolutions.de<\/strong>. Information about the hotel, affected booking, travel period and time of contact is particularly helpful.<\/p>`,\n\n        \"measures.eyebrow\": \"Measures\",\n        \"measures.title\": \"What we are doing\",\n\n        \"measures.closed\": `<h3>Vulnerability closed<\/h3><p>The identified vulnerability was closed on 19 September 2026.<\/p>`,\n\n        \"measures.interfaces\": `<h3>Interfaces further secured<\/h3><p>Authentication and access controls on relevant interfaces, as well as the monitoring of our systems, have been strengthened. Other PMS and data interfaces are being reviewed and further secured.<\/p>`,\n\n        \"measures.contacts\": `<h3>Transfer of contact details reduced<\/h3><p>The transfer of email addresses and phone numbers to connected systems has been restricted; contact details in confirmations are being more extensively masked.<\/p>`,\n\n        \"measures.functions\": `<h3>Functions temporarily restricted as a precaution<\/h3><p>Individual functions were temporarily disabled until the associated access paths had been secured.<\/p>`,\n\n        \"measures.review\": `<h3>External cybersecurity specialist selected<\/h3><p>A company specialising in cybersecurity and incident response has been selected. The scope of the independent investigation and security review is currently being agreed.<\/p>`,\n\n        \"measures.authorities\": `<h3>State Criminal Police Office informed and new cases analysed<\/h3><p>The incident has been reported to the State Criminal Police Office (Landeskriminalamt). New suspicious cases are included in the ongoing analysis.<\/p>`,\n\n        \"faq.title\": \"Frequently asked questions\",\n\n        \"faq.happened.q\": \"What happened?\",\n        \"faq.happened.a\": `<p>A technical vulnerability in an interface between HotelControl and a connected hotel system (PMS) at HotelNetSolutions was exploited. Manipulated requests made it possible to retrieve booking information beyond the scope originally intended for that interface.<\/p><p>In connection with the incident, booking information of this kind is being used to send highly convincing phishing messages to hotel guests. These include messages before arrival, for example about check-in or payments, as well as emails after departure, for example about alleged additional charges or refunds.<\/p>`,\n\n        \"faq.data.q\": \"Which data may be affected?\",\n        \"faq.data.a\": `<p>Based on the cases known to us so far, the following booking information in particular may have been affected:<\/p><ul><li>hotel name and booking number<\/li><li>guest name<\/li><li>contact details such as email address and phone number<\/li><li>arrival and departure dates<\/li><li>total booking amount<\/li><\/ul><p>The information involved may vary from one booking to another.<\/p>`,\n\n        \"faq.closed.q\": \"Has the vulnerability been closed?\",\n        \"faq.closed.a\": `<p>Yes. The identified vulnerability was closed on 19 September 2026. The technical and organisational follow-up is continuing.<\/p>`,\n\n        \"faq.period.q\": \"What time period are we talking about?\",\n        \"faq.period.a\": `<p>The start date and full extent of the unauthorised access cannot currently be determined reliably in retrospect.<\/p><p>Reported phishing cases relate to reservations from a broader period. However, the booking or travel date of a reservation is not the same as the date on which unauthorised access took place.<\/p><p>Reconstructing the timeline is part of the ongoing investigation.<\/p>`,\n\n        \"faq.ongoing.q\":\n          \"Why can phishing messages still appear after the vulnerability was closed?\",\n        \"faq.ongoing.a\": `<p>Closing the vulnerability prevents further access through the identified attack path. Information that had already been accessed without authorisation can, however, continue to be used for fraud attempts.<\/p><p>This also applies after a stay. We are currently seeing emails about alleged additional charges or refunds that direct guests to a link. Such links should not be opened without checking them first; if in doubt, the message should be verified directly with the hotel using known contact details.<\/p>`,\n\n        \"faq.payment.q\": \"Were credit card or payment details exfiltrated?\",\n        \"faq.payment.a\": `<p>Based on the information currently available, there is no indication that credit card or other payment data was exfiltrated through the identified vulnerability at HotelNetSolutions.<\/p><p>This is separate from payment or login details that a guest may subsequently have entered on a fraudulent website.<\/p>`,\n\n        \"faq.q4\": `<span class=\"faq__audience\">For guests<\/span>I have received a suspicious message. What should I do?`,\n        \"faq.a4\":\n          \"If in doubt, do not open any links it contains and do not make any payment through them. Check the message directly with the hotel using a contact channel you already know, for example the official website or phone number.\",\n\n        \"faq.q5\": `<span class=\"faq__audience\">For guests<\/span>How can I tell whether a message really comes from my hotel?`,\n        \"faq.a5\":\n          \"Unfortunately, not always reliably. Correct details such as your name, travel dates or booking number are not proof that a message is genuine. In particular, check whether the service used and the web address really belong to your hotel.\",\n\n        \"faq.q6\": `<span class=\"faq__audience\">For guests<\/span>I have already entered data or paid. What should I do?`,\n        \"faq.a6\":\n          \"If you entered login details, change the password concerned via the official website or app. If you entered bank or credit card details or have already paid, please contact your bank, card provider or the payment provider used immediately.\",\n\n        \"faq.pms.q\": `<span class=\"faq__audience\">For hotels<\/span>Are the connected PMS systems also affected?`,\n        \"faq.pms.a\": `<p>The vulnerability we identified was in an <strong>interface between HotelControl and a connected hotel system (PMS)<\/strong>. Manipulated requests made it possible to retrieve booking data beyond the scope originally intended for that interface.<\/p><p><strong>Based on the information currently available, we have no indication of a vulnerability in the connected PMS systems themselves.<\/strong> Our customers therefore currently do not need to take any action with their PMS provider.<\/p>`,\n\n        \"faq.q7\": `<span class=\"faq__audience\">For hotels<\/span>How can we inform our guests?`,\n        \"faq.a7\": `HotelNetSolutions provides hotel customers with a <a data-guest-comms-link>communication generator<\/a>. You can use it to create a guest notice, a guest FAQ and an FAQ for reception and reservations \u2013 tailored to the check-in, registration and payment services your hotel actually uses.`,\n\n        \"faq.q8\": `<span class=\"faq__audience\">For hotels<\/span>How do we report a new suspected case?`,\n        \"faq.a8\": `Please report new suspicious cases to <a href=\"mailto:info@hotelnetsolutions.de\">info@hotelnetsolutions.de<\/a>. If possible, keep the original message, the sender or phone number, the time and the URL or domain used.`,\n        \"contact.title\": \"Any further questions or information?\",\n\n        \"contact.text\":\n          \"If you have received a suspicious message or need further information, you can contact us by phone or email.\",\n\n        \"contact.hours\": \"By phone Monday \u2013 Friday, 9 am \u2013 5 pm\",\n        \"archive.eyebrow\": \"Archive\",\n\n        \"archive.title\": \"Previous updates\",\n\n        \"archive.note1\":\n          \"The following updates document the state of knowledge at the respective time. Some earlier assessments were later supplemented or superseded by new findings.\",\n\n        \"archive.note2\":\n          \"The current status at the top of this page is what applies.\",\n\n        \"archive.lang\": \"en\",\n\n        \"archive.2026-09-25.stand\": \"As of 25 September 2026\",\n        \"archive.2026-09-25.body\": `<h4><strong>Current status of the phishing incidents.<\/strong><\/h4>\n<p>We have no indication of a vulnerability in the connected PMS systems. Based on the information currently available, our customers therefore do not need to take any action with their PMS provider.<\/p>\n<p>The period from October 2025 through 19 September 2026 refers to the period of the reservations for which corresponding phishing cases were reported. This period must not be equated with the duration of unauthorised access. We have no evidence of access continuing over a period of months.<\/p>\n<p>In retrospect, we cannot reliably determine the exact point in time at which the vulnerability first existed or was actually exploited by unauthorised third parties.<\/p>\n<p>However, as part of our further log analysis, we have now found a technical indication suggesting that an attack on the identified vulnerability had taken place by 20 August 2026 at the latest.<\/p>`,\n\n        \"archive.2026-09-21.stand\": \"As of 21 September 2026\",\n        \"archive.2026-09-21.body\": `<h4><strong>What happened?<\/strong><\/h4>\n<p>On <strong>19 September 2026 at around 14:00<\/strong>, we were able to confirm and close a vulnerability in an interface between HotelControl and a connected hotel system (PMS).<\/p>\n<p>Through this interface, manipulated requests made it possible to access booking data beyond the scope of the functionality originally intended.<\/p>\n<p>Data demonstrably affected included:<\/p>\n<ul>\n<li>hotel name and booking number<\/li>\n<li>guest name and contact details<\/li>\n<li>arrival and departure dates<\/li>\n<li>total booking amount<\/li>\n<li>phone number<\/li>\n<\/ul>\n<p><br \/>We still have no indication that credit card or other payment data was exfiltrated.<\/p>\n<h4><strong>What measures have we taken:<\/strong><\/h4>\n<p>The confirmed vulnerability was closed immediately.<\/p>\n<p>We had already implemented, and have since added, numerous protective measures, including:<\/p>\n<ul>\n<li>additional security measures and reviews for interfaces,<\/li>\n<li>restrictions on the transfer of email addresses and phone numbers to connected systems,<\/li>\n<li>additional authentication and access-control measures,<\/li>\n<li>reviews of other PMS interfaces for comparable vulnerabilities,<\/li>\n<li>masking email addresses and phone numbers more extensively in future confirmation emails,<\/li>\n<li>temporarily disabling individual functions until the associated interfaces had been fully secured.<\/li>\n<\/ul>\n<p>The temporarily restricted data transfers will be re-enabled step by step once they have been successfully reviewed and secured.<br \/>Our systems continue to be closely monitored for unusual access and suspicious activity.<\/p>\n<h2>Please remain vigilant<\/h2>\n<p>Particularly important: We are now also aware of comparable phishing cases involving hotels that do not use systems from&nbsp;HotelNetSolutions.<\/p>\n<p>The phishing attacks currently occurring therefore appear not to be limited to a single system provider or a single technical attack path.<\/p>\n<p>Please therefore continue to raise awareness among your staff and guests.<\/p>\n<p>Hotel guests should in particular not follow unexpected payment requests received via WhatsApp or other messenger services without checking them, and should not enter credit card or payment details via links sent in such messages.<\/p>\n<p>HotelNetSolutions does not ask guests via WhatsApp to enter or confirm credit card or payment details.<\/p>\n<p>By identifying and closing the vulnerability on 19 September 2026, the technical cause of the unauthorised access identified at HotelNetSolutions was resolved. Further securing and monitoring our systems continues to be a top priority.<\/p>`,\n\n        \"archive.2026-09-18.stand\": \"As of 18 September 2026\",\n        \"archive.2026-09-18.body\": `<h2>Current status of the investigation<\/h2>\n<p>The number of reported cases continues to increase. A more differentiated picture has now emerged:<\/p>\n<p>We are receiving reports of phishing cases in which the underlying reservations were processed through our systems, as well as cases in which, based on our investigation to date, the reservation data known to the perpetrators did not originate from our systems.<\/p>\n<p>The period covered by the affected reservations has also expanded. Based on the information currently available, reservations from January 2026 through 13 September 2026 are being reported to us.<\/p>\n<p>This means that the initially apparent concentration on a narrowly defined booking period can no longer be confirmed. The different booking periods and the various sources of the reservation data are part of our further investigation.<\/p>\n<h4><strong>Technical investigations<\/strong><\/h4>\n<p>We have carried out further investigations of the relevant systems, access paths and interfaces.<\/p>\n<p>Based on the current status of our technical investigations, there is no demonstrable unauthorised third-party access to the logins or interfaces used for the booking or communication processes.<\/p>\n<p>Our analysis of the IP addresses used with the relevant interfaces has also not yet identified any anomalies indicating unauthorised access.<\/p>\n<p>The external ASV security scan carried out during the previous night was completed successfully. The scan did not identify any security-related findings that would have caused the scan to fail.<\/p>\n<p>These results are important findings for our ongoing root-cause analysis. However, they do not constitute a final conclusion regarding the cause of the phishing incidents. We are therefore continuing to investigate the other data flows, interfaces and systems involved.<\/p>\n<h4><strong>Investigation of connected systems and partners<\/strong><\/h4>\n<p>For the processing of guest data in connection with OnePageBooking reservations, we do not use any additional service providers to process this guest data.&nbsp;<\/p>\n<p>At the same time, there are interfaces to external systems and partners. These interfaces and the associated data flows form part of our ongoing investigation.&nbsp;<\/p>\n<p>We are in close contact with the relevant partners about this. Our partners have also used the reports received as an opportunity to conduct comprehensive reviews of their own systems and interfaces.&nbsp;<\/p>\n<p>As part of these reviews, vulnerabilities were identified at individual partners. The respective partners have corrected or resolved these issues. The findings from these reviews are being incorporated into our further root-cause analysis.<\/p>\n<h2>Protective measures already implemented<\/h2>\n<p>Regardless of whether individual technical access paths can ultimately be confirmed as the cause of the reported phishing cases, we have already implemented additional technical and organisational measures.&nbsp;<\/p>\n<p>These include, among other things:&nbsp;<\/p>\n<ul><li>additional authentication mechanisms on relevant interfaces,&nbsp;<\/li><\/ul>\n<ul><li>disabling or removing interfaces that are no longer required,&nbsp;<\/li><\/ul>\n<ul><li>additional validation when booking data is changed,&nbsp;<\/li><\/ul>\n<ul><li>additional access restrictions,&nbsp;<\/li><\/ul>\n<ul><li>automatic blocking mechanisms for suspicious access patterns,&nbsp;<\/li><\/ul>\n<ul><li>further securing the Protel integration, and&nbsp;<\/li><\/ul>\n<ul><li>further development of the relevant interface using modern token-based authentication.&nbsp;<br \/><br \/><\/li><\/ul>\n<p>The measures already implemented are reviewed continuously and expanded where necessary.&nbsp;<\/p>\n<h2>Currently no indication that payment data was exfiltrated<\/h2>\n<p>The phishing messages reported to us are intended to persuade guests, by referring to genuine reservations, to enter payment or credit card details.&nbsp;<\/p>\n<p>Based on the information currently available, we have no indication that credit card or other payment data processed by us was exfiltrated.&nbsp;<\/p>\n<p>The fact that individual guests have suffered a financial loss following such a phishing attempt does not mean that the payment data used in that case originated from our systems. These cases are also being taken into account as part of the ongoing investigations.&nbsp;<\/p>\n<h2>Further payment requests sent to guests<\/h2>\n<p>We have now also received reports of cases in which guests were asked again to pay for an existing reservation, even though the reservation was already in place or, in some cases, payment had not yet been made.&nbsp;<\/p>\n<p>In these cases too, the perpetrators refer to specific booking information and try to persuade guests to make payments via a link or payment method specified by them.&nbsp;<\/p>\n<p>We therefore expressly ask our customers to inform their guests about the phishing attempts currently known and raise awareness of such messages.&nbsp;<\/p>\n<h2>Please inform your guests<\/h2>\n<p>As a precaution, please inform your guests that phishing messages relating to hotel reservations are currently circulating.&nbsp;<\/p>\n<p>HotelNetSolutions does not ask guests via WhatsApp to confirm an existing hotel reservation by entering credit card or payment details.&nbsp;<\/p>\n<p>Guests should therefore:&nbsp;<\/p>\n<ul><li>not provide payment or credit card details in response to such a message,&nbsp;<\/li><\/ul>\n<ul><li>not open links in corresponding WhatsApp messages,&nbsp;<\/li><\/ul>\n<ul><li>not make payments using payment methods stated in such messages,&nbsp;<\/li><\/ul>\n<ul><li>if in doubt, contact the hotel directly using the known official contact details and verify whether a payment request is genuine.&nbsp;<\/li><\/ul>\n<p><br \/>Please make your guests particularly aware that such a message does not come from you or your service providers.&nbsp;<\/p>\n<p>From our perspective, informing guests and raising their awareness is an important additional measure to prevent successful misuse of reservation information that has already become known.<\/p>\n<h2>What happens next?<\/h2>\n<p>Our technical investigation is continuing with high priority. We continue to examine possible connections between the different cases and investigate the origin of the reservation information known to the perpetrators.&nbsp;<\/p>\n<p>Our technical investigations to date have found no demonstrable unauthorised third-party access to the logins or relevant booking and communication interfaces examined. At the same time, the investigations of connected systems, data flows and external interfaces are continuing.&nbsp;<\/p>\n<p>If new reliable findings emerge, particularly regarding the cause, scope, affected data or any further protective measures required, we will inform our customers accordingly.&nbsp;<\/p>\n<p>We thank our customers for promptly passing on further suspicious cases and continue to ask for their support in raising awareness among their guests.&nbsp;<\/p>\n<p><strong>We ask for your understanding that investigating the incident currently has the highest priority. Due to the very large number of reports and enquiries we are now receiving, we cannot immediately review and respond to every individual case separately. We therefore first consolidate the information and prioritise the overall technical analysis so that possible connections and the cause can be determined reliably as quickly as possible.<\/strong>&nbsp;<\/p>`,\n\n        \"archive.2026-09-16.stand\": \"As of 16 September 2026\",\n        \"archive.2026-09-16.body\": `<p>Since our last information of 11 September 2026, we have continued the technical investigation of the reported phishing incidents with high priority. Our objective remains to fully clarify the cause and possible connections across the systems, interfaces and processing steps involved and to derive any further protective measures required.<\/p>\n<p>The investigations are not yet complete. In particular, we are still examining how the reservation information known to the unknown third parties may have been obtained and whether there is a common technical connection between the cases known so far.<\/p>\n<h2>Current status<\/h2>\n<p>We have carried out further analysis of the relevant technical interfaces and access paths, with particular attention to those endpoints through which personal data is processed or transmitted within our applications and connected systems.<\/p>\n<p>Our frontend and backend teams are working closely together on this. As a first step, the frontend team identified the interfaces used by the relevant applications <strong>OPB5, OPB6 and VB3<\/strong> and analysed them with regard to the processing of personal data. This overview was then passed to our backend team so that the corresponding interfaces could also be reviewed fully on the backend side.<\/p>\n<p>The investigation therefore covers the individual system components. Further technical measures are being implemented or assessed on the basis of the results.<\/p>\n<p><strong>Based on the information currently available to us, the cases reported so far predominantly concern reservations that were booked between 29 August 2026 and 1 September 2026 inclusive.<\/strong> We have also received isolated reports relating to reservations outside this booking period. Based on our investigation to date, however, these were reservations recorded outside our systems. The investigations into this are continuing.<\/p>\n<p><strong>At this time, we still have no confirmed findings of a compromise of our systems or a successful attack on our systems.<\/strong> However, because the investigations are still ongoing, a connection with possible unauthorised access cannot yet be conclusively ruled out.<\/p>\n<h2>Immediate measures already implemented<\/h2>\n<p>Regardless of the ongoing root-cause analysis, we have already implemented additional technical protective measures to further secure the relevant access paths and reduce the risk of misuse.<\/p>\n<p>These include, among other things:<\/p>\n<ul>\n<li><strong>Additional authentication:<\/strong> Additional authentication has been introduced on relevant interfaces.<\/li>\n<li><strong>Disabling interfaces that are no longer required:<\/strong> Certain endpoints have been removed or disabled.<\/li>\n<li><strong>Additional validation:<\/strong> When booking data is changed, an additional check is now performed to verify that the specified booking group ID actually belongs to the booking being changed.<\/li>\n<li><strong>Additional access restrictions:<\/strong> For an endpoint previously used for the Protel hotel management system.<\/li>\n<li><strong>Automatic blocking mechanisms:<\/strong> If more than 10 requests are made within two minutes, the relevant IP address is blocked for one hour. Repeated incorrect username and password combinations result in the IP address being blocked for four hours.<\/li>\n<li><strong>Further development of the Protel integration:<\/strong> In parallel, we are working on a new JWT-token-based interface for the Protel integration to further improve authentication and the security of the relevant access.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>These measures are precautionary and independent of whether individual technical access paths can ultimately be confirmed as the cause of the reported phishing cases.<\/p>\n<h2>Further technical investigations<\/h2>\n<p>In addition to the immediate measures already implemented, we continue to systematically review the interfaces through which personal data is processed or transmitted.<\/p>\n<p>In particular, we are examining:<\/p>\n<ul>\n<li>which personal data is processed through the respective interfaces,<\/li>\n<li>which systems and components are involved in the respective data flows,<\/li>\n<li>which access and authentication mechanisms are used,<\/li>\n<li>which external or connected systems and service providers are involved in the respective processing steps, and<\/li>\n<li>whether common technical connections can be derived from the cases known so far.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>The results of these analyses are continuously compared between our teams and form the basis for further technical and organisational measures.<\/p>\n<h2>What does this mean for you?<\/h2>\n<p>The recommendations from our information of 11 September 2026 remain unchanged.<\/p>\n<p>Please continue to raise awareness among your employees, particularly the teams responsible for reservations, about the attack pattern currently known.<\/p>\n<p><strong>Important: No payment details via WhatsApp<\/strong><\/p>\n<p>HotelNetSolutions does not request credit card or other payment details via WhatsApp to confirm an existing reservation.<\/p>\n<p>Such messages should not be answered, links contained in them should not be opened, and no payment or credit card details should be entered using the methods specified in them.<\/p>\n<p>If you identify further cases, we continue to ask you to report them to us as promptly as possible. For the ongoing root-cause analysis, particularly helpful information includes the hotel concerned, the booking date and booking channel, arrival and departure dates, the time of the fraudulent contact and, where available, screenshots of the message received and the sender number used.<\/p>\n<p>Please continue to provide only the personal data required for the investigation.<\/p>\n<h2>What happens next?<\/h2>\n<p>Our technical investigation is continuing with high priority. We remain focused on fully reconstructing the cause of the incidents and the possible path by which the affected reservation information may have been obtained.<\/p>\n<p>In parallel, we are implementing additional protective measures and reviewing further technical access paths, interfaces and data flows. If the ongoing investigations produce new reliable findings, particularly regarding the cause, scope, affected data or any further protective measures required, we will inform you without delay.<\/p>\n<p>We thank you for your support and for promptly passing on further suspicious cases. Clarifying the incidents and further securing our systems continue to be our highest priorities.<\/p>\n<p>Thank you for your understanding and support.<\/p>`,\n\n        \"archive.2026-09-11.stand\": \"As of 11 September 2026\",\n        \"archive.2026-09-11.body\": `<p>We are currently aware of several reports from hotels concerning targeted&nbsp;phishing incidents involving hotel guests.&nbsp;Based on the information now available, we would like to inform you as a precaution about the current situation and the measures we have initiated.<\/p>\n<p>According to the reports received so far, guests are being contacted by unknown third parties via WhatsApp using foreign phone numbers and, with reference to genuine hotel reservations, are being asked to confirm their reservation by providing credit card or payment details.<\/p>\n<h2>What happened?<\/h2>\n<p>According to the reports received so far, guests are being contacted by unknown third parties via WhatsApp using foreign phone numbers and, with reference to genuine hotel reservations, are being asked to confirm their reservation by providing credit card or payment details.<\/p>\n<h2>What information is affected?<\/h2>\n<p>Based on the information currently available, the persons involved have at least specific reservation information, in particular the guest's name, the name of the hotel and the respective arrival and departure dates. In the cases investigated so far, there are also anomalies relating to the booking date, which are currently being examined more closely.<\/p>\n<p>We are currently investigating where this data originated and at what point in the processing chain possible unauthorised access or a data leak may have occurred.<\/p>\n<h2>What are we doing?<\/h2>\n<p>Since receiving the first reports on 9 September 2026, we have been investigating our systems and the relevant interfaces with high priority for possible vulnerabilities, unauthorised access and other suspicious activity. This includes evaluating relevant log and access data and analysing IP access. In parallel, we are in contact with our technical partners and the relevant service providers connected to the booking process in order to identify possible connections along the processing chain.<\/p>\n<p><strong>Current state of knowledge<\/strong><\/p>\n<p>Based on the information currently available, we have no confirmed findings of a compromise of our systems or a successful attack on our systems. However, because the investigations are still ongoing, such a compromise cannot yet be conclusively ruled out.<\/p>\n<p>Of particular relevance to the further root-cause analysis is that we are also aware of at least one case in which, based on the information currently available to us, the specific reservation data used in the phishing message was not present in our systems. We are therefore currently investigating in particular which other systems, interfaces, service providers or other processing steps the known cases have in common. The specific cause and source of the possible data leak remain open at present.<\/p>\n<h2>Information for hotels regarding the GDPR<\/h2>\n<p>As the hotel, you are generally the controller within the meaning of the GDPR with regard to your guests' data. We therefore ask you to assess the matter on the basis of the information available to you, including with regard to your obligations under Article 33 and, where applicable, Article 34 GDPR. To the extent that we process the relevant data for you as a processor, this information is also provided as a precaution with regard to our information and assistance obligations under Article 33(2) GDPR.<br \/><br \/>When carrying out your risk assessment, please take particular account of the fact that the reservation information apparently known to the unknown third parties is already being used specifically to persuade guests to disclose credit card or payment details. Based on the information currently available to us, however, there are no indications that credit card or payment data stored by us is the subject of a possible data leak.&nbsp;<\/p>\n<h2>What measures do we recommend?<\/h2>\n<p>Regardless of the outcome of the ongoing investigations, as a precaution we recommend reviewing the credentials of the relevant user accounts and changing passwords where appropriate. Please use strong, unique passwords. The devices used and connected systems should also be checked to ensure they are up to date and for any possible anomalies.<\/p>\n<p>We also recommend informing employees who have contact with guests, particularly the teams responsible for reservations, about the attack pattern currently known.<\/p>\n<p><strong>Important: No payment details via WhatsApp<\/strong><\/p>\n<p>Please also inform your employees and affected guests that HotelNetSolutions does not request credit card or payment details via WhatsApp to confirm an existing reservation. Such requests should not be followed and links contained in the messages should not be opened. Guests who have received such messages should in particular not enter credit card or other payment details in response to those messages or via links contained in them.<\/p>\n<p><strong>What should you do if further cases occur?<\/strong><\/p>\n<p>Please inform us as promptly as possible of any further cases that become known. For the root-cause analysis, particularly helpful information includes the hotel concerned, the booking date and booking channel, arrival and departure dates, the time of the fraudulent contact and, where available, screenshots of the message received and the sender number used. Please provide only the personal data required for the investigation.<\/p>\n<h2>What happens next?<\/h2>\n<p>Our technical investigation is continuing with high priority. As soon as new reliable findings become available, particularly regarding the cause, scope, affected data or protective measures required, we will inform you without delay.<\/p>\n<p>We regret the inconvenience caused and assure you that we are pursuing the investigation of the incidents with high priority.<\/p>\n<p>Thank you for your understanding and support.<br \/><br \/>Kind regards<br \/>Sebastian D\u00fcpr\u00e9<br \/>Head of Operations<\/p>`,\n\n      };\n\n      const LANGS = [\"de\", \"en\"];\n      const originals = new Map();\n\n      function langFromUrl() {\n        \/\/ Same behavior as the previous Elementor app: \/en\/ means English.\n        \/\/ Query-string override remains useful for preview\/testing.\n        const override = new URLSearchParams(window.location.search).get(\n          \"lang\",\n        );\n        if (LANGS.includes(override)) return override;\n        const parts = window.location.pathname\n          .split(\"\/\")\n          .filter(Boolean)\n          .map((part) => part.toLowerCase());\n        return parts.includes(\"en\") ? \"en\" : \"de\";\n      }\n\n      function attrPairs(el) {\n        return (el.dataset.i18nAttr || \"\")\n          .split(\";\")\n          .map((pair) => pair.split(\"=\").map((part) => part.trim()))\n          .filter(([name, key]) => name && key);\n      }\n\n      function remember(el) {\n        if (originals.has(el)) return originals.get(el);\n        const attrs = {};\n        if (el.dataset.i18nAttr) {\n          for (const [name] of attrPairs(el))\n            attrs[name] = el.getAttribute(name);\n        }\n        const entry = { html: el.dataset.i18n ? el.innerHTML : null, attrs };\n        originals.set(el, entry);\n        return entry;\n      }\n\n      function applyPageTexts(lang, dict = {}) {\n        const translate = (key, fallback) =>\n          lang === \"de\" || dict[key] === undefined ? fallback : dict[key];\n        for (const el of document.querySelectorAll(\n          \"[data-i18n], [data-i18n-attr]\",\n        )) {\n          const original = remember(el);\n          if (el.dataset.i18n)\n            el.innerHTML = translate(el.dataset.i18n, original.html);\n          if (el.dataset.i18nAttr) {\n            for (const [name, key] of attrPairs(el))\n              el.setAttribute(name, translate(key, original.attrs[name]));\n          }\n        }\n        document.documentElement.setAttribute(\"lang\", lang);\n      }\n\n      \/\/ Preserved from config.js. Fill this in once the final guest-communication URL is known.\n      const GUEST_COMMUNICATION_URL = \"\";\n      const PLACEHOLDER_HREF = \"#\";\n      function applyGuestCommsLinks() {\n        for (const link of root.querySelectorAll(\"[data-guest-comms-link]\")) {\n          link.href = GUEST_COMMUNICATION_URL || PLACEHOLDER_HREF;\n        }\n      }\n\n      const lang = langFromUrl();\n      applyPageTexts(lang, lang === \"en\" ? EN : {});\n      applyGuestCommsLinks();\n    })();\n  <\/script>\n<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Current status<\/p>\n","protected":false},"author":12,"featured_media":45832,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"content-type":"","footnotes":""},"class_list":["post-45899","page","type-page","status-publish","has-post-thumbnail","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Security notice - HotelNetSolutions GmbH<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hotelnetsolutions.de\/en\/security-notice\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Security notice - HotelNetSolutions GmbH\" \/>\n<meta property=\"og:description\" content=\"Current status\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hotelnetsolutions.de\/en\/security-notice\/\" \/>\n<meta property=\"og:site_name\" content=\"HotelNetSolutions GmbH\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/HotelNetSolutions\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-04T01:34:18+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t<meta property=\"og:image:height\" content=\"2401\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"19 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/\",\"url\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/\",\"name\":\"Security notice - HotelNetSolutions GmbH\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/hotelnetsolutions.de\\\/wp-content\\\/uploads\\\/phishing.jpg\",\"datePublished\":\"2026-10-01T02:41:54+00:00\",\"dateModified\":\"2026-11-04T01:34:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/#primaryimage\",\"url\":\"https:\\\/\\\/hotelnetsolutions.de\\\/wp-content\\\/uploads\\\/phishing.jpg\",\"contentUrl\":\"https:\\\/\\\/hotelnetsolutions.de\\\/wp-content\\\/uploads\\\/phishing.jpg\",\"width\":1600,\"height\":2401},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/security-notice\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Security notice\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/\",\"name\":\"HotelNetSolutions GmbH\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#organization\",\"name\":\"HotelNetSolutions GmbH\",\"url\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hotelnetsolutions.de\\\/wp-content\\\/uploads\\\/2022\\\/01\\\/hnslogo_250x97.png\",\"contentUrl\":\"https:\\\/\\\/hotelnetsolutions.de\\\/wp-content\\\/uploads\\\/2022\\\/01\\\/hnslogo_250x97.png\",\"width\":250,\"height\":97,\"caption\":\"HotelNetSolutions GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/hotelnetsolutions.de\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/HotelNetSolutions\\\/\",\"https:\\\/\\\/de.linkedin.com\\\/company\\\/hotelnetsolutions-gmbh\",\"https:\\\/\\\/www.instagram.com\\\/hotelnetsolutions\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Security notice - HotelNetSolutions GmbH","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/","og_locale":"en_US","og_type":"article","og_title":"Security notice - HotelNetSolutions GmbH","og_description":"Current status","og_url":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/","og_site_name":"HotelNetSolutions GmbH","article_publisher":"https:\/\/www.facebook.com\/HotelNetSolutions\/","article_modified_time":"2026-11-04T01:34:18+00:00","og_image":[{"width":1600,"height":2401,"url":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"19 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/","url":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/","name":"Security notice - HotelNetSolutions GmbH","isPartOf":{"@id":"https:\/\/hotelnetsolutions.de\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/#primaryimage"},"image":{"@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/#primaryimage"},"thumbnailUrl":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing.jpg","datePublished":"2026-10-01T02:41:54+00:00","dateModified":"2026-11-04T01:34:18+00:00","breadcrumb":{"@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hotelnetsolutions.de\/en\/security-notice\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/#primaryimage","url":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing.jpg","contentUrl":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/phishing.jpg","width":1600,"height":2401},{"@type":"BreadcrumbList","@id":"https:\/\/hotelnetsolutions.de\/en\/security-notice\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hotelnetsolutions.de\/en\/"},{"@type":"ListItem","position":2,"name":"Security notice"}]},{"@type":"WebSite","@id":"https:\/\/hotelnetsolutions.de\/en\/#website","url":"https:\/\/hotelnetsolutions.de\/en\/","name":"HotelNetSolutions GmbH","description":"","publisher":{"@id":"https:\/\/hotelnetsolutions.de\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hotelnetsolutions.de\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/hotelnetsolutions.de\/en\/#organization","name":"HotelNetSolutions GmbH","url":"https:\/\/hotelnetsolutions.de\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hotelnetsolutions.de\/en\/#\/schema\/logo\/image\/","url":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/2022\/01\/hnslogo_250x97.png","contentUrl":"https:\/\/hotelnetsolutions.de\/wp-content\/uploads\/2022\/01\/hnslogo_250x97.png","width":250,"height":97,"caption":"HotelNetSolutions GmbH"},"image":{"@id":"https:\/\/hotelnetsolutions.de\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/HotelNetSolutions\/","https:\/\/de.linkedin.com\/company\/hotelnetsolutions-gmbh","https:\/\/www.instagram.com\/hotelnetsolutions\/"]}]}},"_links":{"self":[{"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/pages\/45899","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/comments?post=45899"}],"version-history":[{"count":62,"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/pages\/45899\/revisions"}],"predecessor-version":[{"id":46308,"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/pages\/45899\/revisions\/46308"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/media\/45832"}],"wp:attachment":[{"href":"https:\/\/hotelnetsolutions.de\/en\/wp-json\/wp\/v2\/media?parent=45899"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}