ThreatBeaconXSubscribe
HighThreat Intelligence · 23 min read

Dahua IP Cameras Hijacked Through Easy4IP Cloud Access and Authentication Bypass Vulnerabilities

Ukraine's Computer Emergency Response Team (CERT-UA), operating under the State Service of Special Communications and Information Protection of Ukraine (SSSCIP), has warned of unauthorized remote access to Dahua IP cameras and video recorders. The reported incidents involved attackers accessing video streams, modifying device configurations, and creating unauthorized accounts. According to CERT-UA's advisory published on October 23, 2026, and The Hacker News report dated October 27, 2026, the primary access vector involves Dahua's Easy4IP peer-to-peer (P2P) cloud-access functionality. The service allows users to connect remotely to compatible cameras and recorders using a device serial number, without requiring a directly exposed public IP address or publicly accessible inbound port. The reported activity exploits the predictable structure of device serial numbers to identify potential targets. Attackers can then attempt authentication using weak or known passwords or exploit authentication-bypass vulnerabilities in outdated firmware, including CVE-2021-33044 and CVE-2021-33045. The advisory highlights a critical security consideration: devices that are not directly accessible from the internet may still be remotely reachable through cloud-relay infrastructure. Consequently, traditional perimeter controls alone may not adequately protect surveillance equipment when P2P access remains enabled. The Hacker News also described two separate clusters of camera-related activity reported by Hunt.io. One campaign compromised 58 devices in Ukraine while scanning and exploiting multiple camera and network-device vendors across 15 European countries. The second, named Operation CameraSwarm, reportedly compromised more than 14,530 Dahua IP cameras between June 17 and July 22, 2026. Hunt.io reported that 1,923 cameras in the latter campaign received a persistent backdoor account. These campaigns demonstrate the potential for surveillance devices to become targets for unauthorized monitoring, persistent access, and broader intelligence collection. However, CERT-UA has not disclosed the number of devices affected by the specific incidents in its advisory, and the available reporting does not establish that the three activity clusters share the same operator.

Written by VEDANABHATLA SAI SWETHA·Published Oct 29, 2026

1. Description

Internet-connected surveillance equipment has become an important component of residential, commercial, and industrial security. IP cameras, network video recorders (NVRs), and digital video recorders (DVRs) provide remote monitoring capabilities, but their connectivity can also create security risks when remote-access mechanisms are improperly secured.

CERT-UA reported cases involving unauthorized access to Dahua surveillance devices. The recorded activity included access to video streams, unauthorized configuration changes, and the creation of third-party accounts.

The primary access vector identified by CERT-UA is Easy4IP, a P2P cloud-access platform that allows users to remotely monitor compatible Dahua devices through a smartphone application or web browser. Depending on the supported setup, users can connect by scanning a QR code or entering the device's hardware serial number.

The security concern arises from the combination of predictable serial-number structures, cloud-mediated device discovery, and insufficient authentication protection. Attackers may generate candidate serial numbers, identify devices registered with the cloud service, and attempt to access them through weak credentials or vulnerable firmware.

This approach challenges the assumption that a camera is protected simply because it sits behind a router or firewall. When cloud-mediated remote access is enabled, the device may remain reachable without a directly exposed public IP address.

The October 2026 reporting also places the CERT-UA warning within a wider pattern of camera exploitation. Hunt.io previously documented separate activity targeting Dahua and other surveillance or network devices, including a campaign affecting 58 devices and Operation CameraSwarm, which reportedly compromised more than 14,530 Dahua cameras.

Separately, Dutch intelligence agencies warned in July 2026 that Russian actors were compromising IP cameras across European Union and NATO states and Ukraine to collect military-related imagery and information. This illustrates the possible intelligence value of surveillance-device access, but it does not establish a connection between those operations and the specific CERT-UA incidents.

2. Technical Description

2.1 Dahua surveillance devices

Dahua IP cameras and video recorders are network-connected devices used to capture, transmit, and store surveillance footage. Depending on the model, they can provide live video, recording playback, administrative configuration, user management, and remote-access functionality.

An IP camera generally transmits video over a network, while an NVR or DVR can manage recording and playback across one or more cameras. Unauthorized administrative access can therefore expose more than an individual live stream: it may provide access to recorded footage, user settings, and other device-management functions.

The impact of a compromise depends on the affected device, its configuration, the privileges obtained, and the environment in which it is deployed.

2.2 Easy4IP P2P cloud-access architecture

Easy4IP is the principal access vector identified in the CERT-UA advisory.

The reported connection model works at a high level as follows:

  1. A compatible camera or recorder initiates an outbound connection to the manufacturer's cloud infrastructure.

  2. The device registers with the service using its serial number.

  3. An authorized user supplies the relevant device identifier through a supported application or interface.

  4. The cloud service facilitates a connection between the user and the device.

  5. The device can be reached remotely even when it sits behind network address translation (NAT) or a firewall that does not expose the device through a public inbound port.

This architecture simplifies legitimate remote access, but it also means that the security of the device depends partly on the controls protecting its cloud-mediated access path.

Security implication: The absence of a directly exposed camera-management port does not prove that the device is unreachable. Administrators must assess whether remote-access services are enabled and whether their authentication mechanisms are adequately protected.

2.3 Predictable serial-number structure

CERT-UA warned that Dahua serial numbers have a predictable structure that can facilitate large-scale device discovery.

The example reported by The Hacker News is:

7K01F36PCA003E8

The article describes the serial number as containing:

  • A 10-character model prefix, shared by devices in the same device family.

  • A five-character hexadecimal counter, which increases in an almost sequential manner.

The predictable counter can reduce the effort required to generate candidate serial numbers. Attackers can then check whether candidate identifiers correspond to devices registered with the cloud service.

According to CERT-UA, this process can be conducted at scale without encountering rate limits or account lockouts in the reported scenario.

Serial numbers are identifiers, not authentication secrets. Their predictability should not independently grant access, but it can make target discovery easier when combined with weaknesses in cloud access or device authentication.

2.4 Authentication-bypass vulnerabilities

CERT-UA identified two Dahua authentication-bypass vulnerabilities as relevant to the reported threat.

CVE-2021-33044

This vulnerability concerns authentication bypass in affected Dahua products. Depending on the vulnerable product and conditions, an attacker may be able to bypass the normal authentication process.

CVE-2021-33045

This is another authentication-bypass vulnerability affecting certain Dahua products. The reported attack activity uses these vulnerabilities as a potential alternative to credential-based access.

Both vulnerabilities date from 2021. Their relevance to a particular device depends on its exact model and firmware version.

Administrators should verify the applicability of each vulnerability against official vendor security advisories. The presence of a Dahua camera alone does not establish that it is vulnerable, and the available reporting does not identify the exact firmware versions of every compromised device.

2.5 Weak and known credentials

Attackers may also overcome authentication controls by using weak, default, or otherwise known passwords.

Credential-based attacks and authentication bypass are distinct methods:

  • Credential attacks attempt to authenticate using available or guessed account credentials.

  • Authentication bypass exploits a flaw that permits access without completing the expected authentication process.

A device may be exposed to one or both methods, depending on its firmware, account configuration, and remote-access setup.

Consequently, password changes alone are not an adequate response to an unpatched authentication-bypass vulnerability. Likewise, installing firmware updates does not eliminate the risk of weak credentials or unnecessary remote-access exposure.

2.6 DVRIP protocol and local-loopback activity

CERT-UA identified audit-log entries involving Dahua's native DVRIP protocol and the local address 127.0.0.1 as a potential indicator of P2P-related access.

The address 127.0.0.1 is the IPv4 loopback address. In the reported context, authentication events associated with this address may indicate that a connection was handled internally by the device rather than appearing as a conventional direct remote connection.

This is particularly relevant when investigating cloud-mediated access paths, because the source visible in a device's internal audit log may not directly identify the original remote party.

Such an event should be treated as an investigative lead rather than standalone proof of compromise. Analysts should correlate it with account changes, configuration history, device behavior, and other available logs.

2.7 TCP port 37777 and Operation CameraSwarm

The Hacker News reported that Operation CameraSwarm used scanning for TCP port 37777, described as Dahua's default proprietary management and video-streaming port.

According to Hunt.io, the campaign combined device scanning, serial-number collection, credential attacks, and exploitation of CVE-2021-33044 and CVE-2021-33045.

The reporting further states that the operators used Dahua's cloud relay to reach some devices behind NAT by using serial numbers alone.

Port 37777 is therefore a useful investigation point for the separately reported CameraSwarm activity. However, the available sources do not establish that the same scanning behavior occurred in every incident described by CERT-UA.

Organizations should also avoid treating this port as a complete detection signature: a port being present or accessible does not by itself demonstrate malicious activity.

3. Attack Overview

3.1 CERT-UA-reported activity

The October 2026 CERT-UA advisory describes unauthorized access to Dahua IP cameras and recorders through Easy4IP and authentication weaknesses.

The reported consequences include:

  • Unauthorized viewing of video streams.

  • Changes to device configurations.

  • Creation of third-party user accounts.

  • Potential access through predictable serial numbers and cloud-mediated connections.

  • Authentication through weak or known passwords, or exploitation of vulnerable firmware.

CERT-UA did not disclose the identity of the responsible actor, the precise infection period, the total number of compromised devices, or the full list of targeted organizations.

3.2 Related activity cluster 1: Campaign affecting 58 devices

The Hacker News cited Hunt.io reporting on a separate campaign attributed to a Russian-speaking operator. This campaign reportedly targeted internet-exposed cameras in Ukraine and compromised 58 devices.

The reported activity involved known vulnerabilities affecting several vendors:

CVEVendor or product familyReported vulnerability type
CVE-2017-7921HikvisionAuthentication bypass
CVE-2020-25078D-LinkCredential disclosure
CVE-2020-25169ReolinkUnauthenticated information disclosure
CVE-2021-33044DahuaAuthentication bypass
CVE-2021-33045DahuaAuthentication bypass
CVE-2021-36260HikvisionUnauthenticated remote code execution

According to The Hacker News, the activity incorporated Ingram, a publicly available webcam vulnerability scanner, into the exploitation workflow.

The same actor was also reported to have scanned and exploited TP-Link and MikroTik routers and cameras using vulnerabilities including CVE-2024-53375 and CVE-2024-57049.

The article states that this broader activity covered 15 European countries: Ukraine, Poland, Romania, Moldova, Hungary, Czechia, Slovakia, Bulgaria, Germany, France, the Netherlands, Italy, Spain, the United Kingdom, and Austria.

These findings indicate that the reported activity extended beyond Dahua cameras. However, the source does not establish that all devices scanned across these countries were successfully compromised.

3.3 Related activity cluster 2: Operation CameraSwarm

Operation CameraSwarm is a separate campaign that Hunt.io reportedly attributed to a lone threat actor.

According to The Hacker News, the campaign compromised more than 14,530 Dahua IP cameras between June 17 and July 22, 2026.

The reported workflow included:

  1. Scanning for TCP port 37777.

  2. Collecting device serial numbers.

  3. Attempting access using credential attacks and authentication-bypass techniques.

  4. Exploiting CVE-2021-33044 and CVE-2021-33045.

  5. Using Dahua's P2P cloud relay to reach selected devices behind NAT.

  6. Installing a persistent backdoor account on a subset of compromised cameras.

Hunt.io reported that 1,923 cameras received a persistent account associated with the identifiers p2pwn and p2password.

The account was reportedly installed over RPC following authentication bypass. Hunt.io stated that it was stored independently of the administrator password and survived password changes and, on most affected firmware, a factory reset.

Hunt.io also reported that 283 cameras were reached through serial-number-based cloud relay access without a device address and, in most cases, without credentials.

These figures belong specifically to the reported CameraSwarm campaign. They must not be presented as the number of devices affected by the October CERT-UA advisory.

3.4 Separate intelligence context: Camera access for military surveillance

The Hacker News also referenced a July 2026 warning from Dutch intelligence agencies about Russian actors compromising IP cameras across the European Union, NATO states, and Ukraine.

According to the quoted warning, the actor used automated image-recognition software to identify military vehicles and military cargo. The resulting information could reveal transport routes, weapon deliveries to Ukraine, and the locations of Ukrainian military personnel.

The warning stated that imagery from cameras in Ukraine was being used in attempts to neutralize Ukrainian military personnel and destroy military materiel.

This context demonstrates that compromised cameras can have intelligence value beyond ordinary privacy violations. However, the sources provided do not establish that the actor described in the Dutch warning was responsible for the CERT-UA incidents, the 58-device campaign, or Operation CameraSwarm.

3.5 Timeline of key developments

DateEvent
2021Dahua authentication-bypass vulnerabilities CVE-2021-33044 and CVE-2021-33045 were disclosed.
June 17–July 22, 2026Operation CameraSwarm reportedly compromised more than 14,530 Dahua cameras.
July 2026Dutch intelligence agencies warned of camera compromises used to collect military-related intelligence.
October 23, 2026CERT-UA published its warning about unauthorized access to Dahua cameras and recorders through cloud access.
October 27, 2026The Hacker News published its report and contextualized the CERT-UA warning with separate Hunt.io campaign findings.

4. Technical Analysis

4.1 Cloud access changes the exposure model

Traditional network-security assessments often focus on whether a device has an internet-routable address or exposes an inbound management port.

Easy4IP introduces another consideration: the device itself establishes an outbound connection to cloud infrastructure, which facilitates subsequent remote access.

This means a camera can be protected by NAT and still be reachable through an enabled P2P service. The security boundary is no longer determined exclusively by the local firewall.

The practical implication is that organizations should inventory remote-access features separately from public-facing ports. A device with no directly exposed inbound port may still require security hardening because its cloud connection provides a path for legitimate and potentially unauthorized access.

4.2 Serial-number enumeration supports target discovery

Predictable identifiers can make device discovery more efficient.

When a model prefix is shared by a family of devices and a counter follows an almost sequential pattern, an attacker may generate candidate serial numbers and query the service to determine which devices are registered.

This reduces reliance on random discovery and can make target selection more systematic.

However, serial-number enumeration alone is not equivalent to successful compromise. The attacker still needs a viable path through the service and device authentication controls, or a relevant vulnerability that enables unauthorized access.

4.3 Multiple authentication paths complicate remediation

The reported activity uses two broad access methods: credential-based authentication and exploitation of authentication-bypass vulnerabilities.

Each requires a different defensive response.

Access methodSecurity weaknessPrimary defensive response
Weak or known passwordsInadequate credential protectionChange exposed credentials, remove defaults, and review accounts.
Authentication bypassVulnerable firmware or implementationApply the appropriate vendor security update or supported remediation.
Cloud-relay accessUnnecessary or insufficiently protected P2P functionalityDisable P2P when not required and restrict approved remote access.
Persistent unauthorized accountAccount-level persistence after initial accessInvestigate account creation and device integrity; follow verified recovery procedures.

Addressing only one of these areas may leave another route available. For example, a strong password does not remediate an authentication-bypass flaw, while an updated device may remain exposed if its cloud-access configuration and credentials are insecure.

4.4 Persistent accounts create recovery challenges

The CameraSwarm reporting describes a backdoor account that was reportedly independent of the administrator password and, on most affected firmware, survived a factory reset.

If verified on a particular device, this behavior would undermine ordinary recovery assumptions. An administrator might reset the primary password or restore factory settings without eliminating the unauthorized access mechanism.

This is why incident response must begin by identifying the specific model, firmware, symptoms, and applicable campaign evidence. Administrators should not assume that every Dahua device contains the reported account or that the same persistence mechanism is present in the CERT-UA incidents.

Where persistent compromise is suspected, recovery should follow official vendor guidance and a documented incident-response procedure. If device integrity cannot be established, replacement or other vendor-approved recovery measures may be necessary.

4.5 Why the 58-device campaign matters

The separate campaign affecting 58 devices illustrates the breadth of the surveillance-device attack surface.

It involved multiple manufacturers and a collection of disclosed vulnerabilities affecting authentication, credential confidentiality, information disclosure, and remote code execution.

This is important because an organization may operate devices from several vendors. Protecting Dahua cameras alone will not address exposure across Hikvision, D-Link, Reolink, TP-Link, and MikroTik products if those systems are also deployed.

The broader lesson is to manage cameras, recorders, routers, and related network equipment as an integrated IoT security environment rather than as isolated devices.

4.6 Surveillance devices as intelligence sources

Camera compromise can expose more than live footage.

Depending on placement and retention settings, attackers may obtain:

  • Real-time views of people and activities.

  • Recorded footage from earlier periods.

  • Information about entrances, exits, and facility layouts.

  • Operational schedules and recurring movement patterns.

  • Evidence of deliveries, equipment movement, or transport activity.

  • Information that can be correlated with other intelligence sources.

The July 2026 Dutch intelligence warning illustrates how image recognition can help turn camera access into targeted information collection.

Nevertheless, this is broader threat context. The available sources do not demonstrate that the CERT-UA-reported compromises involved military surveillance or that every compromised camera exposed sensitive operational information.

4.7 Limits of the available evidence

The CERT-UA advisory establishes that cases of unauthorized access were recorded and identifies the principal access vector, relevant authentication weaknesses, and recommended defensive measures.

It does not disclose:

  • The total number of affected devices.

  • The identity of the operator.

  • The precise period during which the incidents occurred.

  • A complete list of compromised serial numbers, IP addresses, or domains.

  • The firmware versions of all affected devices.

  • Whether the devices were used for further access to other networks.

  • A confirmed relationship with the separate Hunt.io campaigns.

These gaps should remain explicit in any intelligence assessment. Similar tools, vulnerabilities, or access methods can indicate a shared attack surface without proving a shared actor or operation.

5. Indicators of Compromise (IOCs)

The CERT-UA advisory primarily provides behavioral and device-audit indicators rather than a list of confirmed malicious IP addresses, domains, or file hashes.

5.1 Device and account indicators

IndicatorDescriptionInvestigative significance
Unknown user accountsAccounts that were not created or approved by the device ownerMay indicate unauthorized administrative access or persistence.
Unauthorized configuration changesSettings modified without an approved administrative actionMay indicate that an attacker obtained configuration privileges.
Unexpected video overlaysUnexplained text or graphics appearing over camera footageCERT-UA identifies unauthorized overlays as a possible sign of compromise.
DVRIP authentication eventsAuthentication events involving Dahua's native protocolRequire correlation with legitimate and suspicious device activity.
Local address 127.0.0.1 in DVRIP logsAuthentication events recorded from the loopback addressCERT-UA identifies this as a potential sign of P2P-related access.

The absence of an overlay does not rule out compromise. Likewise, a single audit-log entry involving 127.0.0.1 is not conclusive without supporting evidence.

5.2 Network and service indicators

IndicatorValueContext
Dahua proprietary management and streaming portTCP 37777Reported by Hunt.io in connection with the separate Operation CameraSwarm campaign.
Easy4IP P2P accessEnabled cloud-mediated remote connectivityReview whether the feature is authorized and necessary.
Predictable serial-number structure10-character model prefix plus a five-character hexadecimal counterRelevant to the reported device-discovery method.
Authentication-bypass vulnerabilitiesCVE-2021-33044 and CVE-2021-33045Validate against the device model and firmware version.

These indicators have different evidentiary meanings. TCP port 37777 is a service indicator, not a unique malicious signature. The serial-number pattern describes device identification, not proof of an attack.

5.3 Operation CameraSwarm-specific indicators

The Hacker News report, citing Hunt.io, describes a persistent account associated with the identifiers:

  • p2pwn

  • p2password

These identifiers were associated with the separate Operation CameraSwarm campaign, in which Hunt.io reported that 1,923 cameras received a persistent backdoor account.

Attribution caution: The account identifiers must not be attributed automatically to the devices described in the CERT-UA advisory. Their presence should trigger investigation, but their absence does not rule out compromise through another method.

5.4 Vulnerability indicators

The following CVEs are relevant to the reported activity:

  • CVE-2021-33044: Dahua authentication bypass.

  • CVE-2021-33045: Dahua authentication bypass.

  • CVE-2017-7921: Hikvision authentication bypass, referenced in the separate 58-device campaign.

  • CVE-2020-25078: D-Link credential disclosure, referenced in the separate campaign.

  • CVE-2020-25169: Reolink unauthenticated information disclosure, referenced in the separate campaign.

  • CVE-2021-36260: Hikvision unauthenticated remote code execution, referenced in the separate campaign.

  • CVE-2024-53375 and CVE-2024-57049: Referenced in The Hacker News reporting about the broader TP-Link and MikroTik scanning and exploitation activity.

The latter vulnerabilities should not be interpreted as confirmed causes of the CERT-UA-reported Dahua incidents. Their inclusion reflects the separate campaign context described by The Hacker News.

5.5 IOC limitations

The available sources do not provide a confirmed set of malicious IP addresses or domains specific to the October CERT-UA incident.

Security teams should therefore avoid inventing network indicators or treating every Dahua device as compromised. Device logs, configuration history, firmware status, account records, and validated campaign-specific indicators should be correlated before assigning an incident classification.

6. Potential Impact

6.1 Unauthorized video surveillance

Attackers who gain access to a camera may view live footage or recordings. This can expose employees, residents, visitors, business operations, and sensitive locations.

The scale of the impact depends on the camera's placement, available recording history, and the level of access obtained.

6.2 Physical-security exposure

Surveillance footage can reveal building layouts, entry points, access-control procedures, guard movements, and recurring activity patterns.

Such information may help an attacker understand a facility's security arrangements. In high-risk environments, the resulting exposure can extend beyond privacy into physical-security concerns.

6.3 Military and intelligence collection

The separate Dutch intelligence warning demonstrates that compromised cameras can provide information about military vehicles, cargo movements, transport routes, weapon deliveries, and personnel locations.

Automated image analysis can make large volumes of video more useful to an intelligence operator by helping identify specific objects or activities.

This is a documented broader threat scenario, not a confirmed impact of the specific CERT-UA incident.

6.4 Unauthorized administrative control

Attackers who gain sufficient privileges may alter device settings or create additional accounts. These changes can interfere with legitimate administration and make it harder for the owner to identify the source of unauthorized activity.

Unauthorized configuration changes can also reduce confidence in the integrity of the surveillance system.

6.5 Persistent access

The Operation CameraSwarm findings show that a separate campaign reportedly deployed an account capable of surviving certain password changes and factory resets.

If similar persistence is identified in another incident, ordinary credential rotation may not be sufficient. The device may require a more comprehensive recovery procedure.

6.6 Privacy and regulatory consequences

Unauthorized access to personal or business footage can create privacy, contractual, and regulatory exposure. Organizations may need to determine what data was accessible, how long the compromise lasted, and whether notification obligations apply.

The actual obligations depend on the jurisdiction, data involved, and applicable legal requirements.

6.7 Broader network compromise

The available sources do not establish that the CERT-UA incident led to compromise of connected enterprise networks. Nevertheless, a poorly segmented camera network can increase risk if an attacker attempts to use compromised equipment to access other systems.

Organizations should assess the camera's network permissions and investigate any unusual communication with internal services.

6.8 Loss of trust in surveillance systems

If administrators cannot verify device integrity after a compromise, footage and configuration data may become less trustworthy. Organizations may need to validate device settings, review access history, and assess whether monitoring coverage was disrupted or manipulated.

7. Recommendations

7.1 Immediate Actions

1. Disable Easy4IP P2P/cloud access when unnecessary

Review every camera and recorder to determine whether cloud-mediated access is required. Disable P2P/Cloud Access on devices that do not need it.

If remote viewing is required, establish an approved alternative with appropriate access restrictions and monitoring.

2. Inspect local and cloud-linked accounts

Review local device users, administrator accounts, and linked cloud accounts. Remove unauthorized accounts and disconnect unknown cloud associations after preserving relevant evidence.

3. Update the device firmware

Identify the exact model and installed firmware version. Apply the relevant vendor security updates and verify that CVE-2021-33044 and CVE-2021-33045 are addressed where applicable.

If a device is no longer supported, assess whether it should be replaced.

4. Replace weak or default passwords

Set unique, strong credentials for each device and administrative account. Remove default credentials and review whether exposed passwords were reused elsewhere.

If unauthorized access is suspected, rotate affected credentials from a trusted system.

5. Review audit logs

Examine device logs for unknown accounts, unexplained configuration changes, and DVRIP authentication events involving 127.0.0.1.

Correlate timestamps with administrator activity, remote-access sessions, and other available network records.

6. Restrict internet exposure

Avoid exposing camera and recorder management interfaces directly to the public internet. Use a properly secured VPN or another approved remote-access mechanism and restrict access to authorized systems or addresses.

7. Investigate TCP port 37777 exposure

For environments using Dahua equipment, determine whether TCP port 37777 is reachable from untrusted networks and whether such access is necessary.

The port is particularly relevant to the separately reported CameraSwarm campaign, but exposure alone does not establish compromise.

8. Investigate suspected persistence

If an unknown account or other evidence suggests a persistent compromise, preserve device logs and configuration evidence before attempting recovery.

Do not assume that changing the administrator password or performing a factory reset will always restore device integrity. Follow verified vendor guidance for the specific model and suspected compromise.

9. Preserve evidence and report incidents

Record affected device models, serial numbers, firmware versions, timestamps, account changes, configuration changes, and relevant network activity.

CERT-UA advises reporting suspected unauthorized access by email to cert@cert.gov.ua.

7.2 Preventive Actions

1. Maintain an inventory of surveillance devices

Document device models, serial numbers, firmware versions, network locations, owners, linked cloud accounts, and remote-access settings.

This inventory helps identify devices requiring updates or configuration changes.

2. Minimize cloud-access exposure

Disable unnecessary P2P services. Where remote access is required, ensure that it is explicitly authorized and supported by appropriate authentication, network restrictions, and monitoring.

3. Apply regular firmware updates

Establish a defined process for reviewing vendor security advisories, testing updates where appropriate, and deploying patches within risk-based deadlines.

Prioritize devices exposed to remote access and those affected by known authentication-bypass vulnerabilities.

4. Enforce strong authentication

Use unique administrative credentials, remove default accounts where supported, and limit the number of users with administrative privileges.

Credential management should be combined with firmware maintenance and remote-access restrictions.

5. Segment surveillance networks

Place cameras and recorders on dedicated network segments. Restrict communication with corporate workstations, servers, identity systems, and sensitive infrastructure unless explicitly required.

6. Monitor administrative changes

Enable available logging and alert on account creation, privilege changes, remote-access modifications, and unexplained configuration changes.

Retain logs long enough to support incident investigation.

7. Establish device recovery procedures

Document how to isolate a camera, preserve evidence, validate firmware, restore a trusted configuration, and confirm device integrity after a suspected compromise.

Include a contingency for replacing devices whose integrity cannot be established.

8. Assess all IoT vendors

Review cameras, recorders, routers, and related equipment across the environment. Do not limit vulnerability management to Dahua if other manufacturers' products are also deployed.

9. Validate remote-access requirements

Periodically review which users, applications, and cloud accounts require access to surveillance devices. Remove obsolete accounts and connections.

10. Train administrators and operators

Ensure that personnel responsible for surveillance equipment understand the risks associated with default passwords, outdated firmware, exposed management interfaces, and unauthorized account changes.

8. Detection and Threat-Hunting Guidance

Security teams should combine device-level evidence with network, authentication, and configuration records to determine whether surveillance equipment has been compromised.

8.1 Detection matrix

Detection areaWhat to investigateSuggested response
User accountsUnknown or unexpected accountsValidate account ownership and investigate creation history.
Configuration changesUnapproved modifications to device settingsCompare against a known-good baseline and restore trusted settings after evidence preservation.
DVRIP logsAuthentication events involving 127.0.0.1Correlate with P2P activity, account changes, and other audit records.
P2P/cloud accessEasy4IP enabled without a documented requirementDisable unnecessary access and assess exposure.
Firmware inventoryModels and versions affected by relevant CVEsValidate vendor guidance and patch or replace vulnerable devices.
Network exposureTCP port 37777 reachable from untrusted networksVerify business necessity and restrict access where appropriate.
Persistent accountsUnexpected p2pwn or p2password identifiersInvestigate using the specific CameraSwarm research as context; do not assume attribution from the account name alone.
Video behaviorUnexpected overlays or unexplained changes in camera operationPreserve footage and device logs, then investigate configuration integrity.
Remote-access recordsUnusual connection times or unauthorized viewing activityCorrelate with authorized-user records and network telemetry.
Adjacent network activityUnexpected communication from surveillance devices to internal systemsInvestigate whether the device is communicating beyond its approved role.

8.2 Firmware and vulnerability validation

Use the device inventory to identify models and firmware versions that may be affected by CVE-2021-33044 or CVE-2021-33045.

Validation should rely on official vendor guidance. A vulnerable product family does not prove that a specific device was exploited, and a device running updated firmware may still require investigation if there is evidence of earlier compromise.

8.3 Cloud-access investigation

For devices with Easy4IP enabled:

  1. Confirm that the feature is required and authorized.

  2. Review linked accounts and device registrations.

  3. Examine device logs for suspicious authentication and configuration activity.

  4. Identify unexpected accounts or changes to remote-access settings.

  5. Restrict access while investigating confirmed or strongly suspected compromise.

  6. Validate device integrity before restoring normal connectivity.

8.4 Campaign-specific hunting

For the separate Operation CameraSwarm campaign, analysts may investigate TCP port 37777, the reported persistent account identifiers, and the two Dahua authentication-bypass vulnerabilities.

These indicators should be used with appropriate context. They are not a substitute for device-specific evidence, and the available reporting does not confirm that the same indicators apply to every incident described by CERT-UA.

For the separate 58-device campaign, teams should assess whether their inventory includes the other affected product families and whether the listed vulnerabilities apply to their installed firmware.

8.5 Correlation and attribution

The three reported activity clusters share a broad focus on surveillance devices and, in some cases, similar authentication weaknesses. That overlap can guide hunting and vulnerability prioritization.

It does not independently prove that the same operator, infrastructure, or campaign was responsible.

Analysts should distinguish confirmed observations from hypotheses and avoid assigning attribution based solely on the presence of a common CVE, device vendor, or access method.

9. Conclusion

The CERT-UA warning highlights a security weakness that extends beyond directly exposed network services: cloud-mediated access can leave surveillance equipment remotely reachable even when the device sits behind NAT or a firewall.

Predictable serial numbers can make target discovery easier, while weak credentials and authentication-bypass vulnerabilities can provide a route to unauthorized access. The reported consequences include access to video streams, configuration changes, and the creation of third-party accounts.

The separate campaigns described by Hunt.io demonstrate the wider threat landscape. One reportedly compromised 58 devices while targeting multiple camera and network-device vendors; Operation CameraSwarm reportedly compromised more than 14,530 Dahua cameras and installed persistent accounts on a subset of them. Separately, Dutch intelligence agencies warned that compromised cameras can support military-related intelligence collection.

These findings should not be conflated into a single operation. The available reporting does not establish the identity of the actor behind the CERT-UA incidents, the total number of devices affected in those incidents, or a confirmed relationship with the other campaigns.

Organizations should disable unnecessary P2P access, update vulnerable firmware, enforce strong credentials, inspect account and configuration changes, restrict network exposure, and monitor surveillance equipment as part of their broader IoT security program.

The key lesson is that a camera does not need a public IP address to be exposed to remote-access risk. Secure cloud connectivity, patched firmware, controlled authentication, and continuous device monitoring are all necessary to reduce the likelihood and impact of compromise.

MITRE ATT&CK Mapping

T1046 — Network Service DiscoveryT1110 — Brute ForceT1190 — Exploit Public-Facing ApplicationT1078 — Valid AccountsT1133 — External Remote ServicesT1136.001 — Create Account: Local Account