Part 2, Hikvision Senior Director of Cybersecurity on Examples of Smishing Hacks, Tips to Prevent Becoming a Victim of this Cyberattack

July 15, 2020

Hikvision HikWire blog article Chuck Davis smishing part 2

5 Tips to Identify and Protect Against Smishing from Hikvision

 

In yesterday’s blog, Hikvision’s Davis discussed an increase in smishing—a phishing hack that uses text messages to target vulnerable parties. Today’s blog will cover examples of smishing and five tips to help you avoid becoming a victim of this cyberattack.

A Refresher: What is Smishing?
Smishing combines the term SMS (text messaging) and the word phishing, a type of phishing that uses SMS and similar types of text messaging. Despite the name, smishing does not have to be delivered as an SMS text message. Smishing attackers will use any form of text or chat messaging that they can, such as Facebook Messenger, WhatsApp, GroupMe, Discord, Slack, or any other text-based mobile application or service.

Examples of Smishing
A smishing message may look like an alert from a courier service, a notification from a well-known bank or company, or even an announcement about the recipient winning a prize. As mobile numbers are tied to so many online accounts, sometimes the attacker will know the name of the target and include that in the message to add credibility. Below are some smishing examples to help you better understand and identify these types of attacks.

How-to Geek shared a package delivery smishing scam that could become very costly for a victim who is not paying close attention to the fine print. This attack starts with an SMS text message, informing the recipient that they have a FedEx package that needs the recipient’s delivery preference.

Hikvision HikWire blog article Smishing part 2, image 1

When the recipient clicks on the link, they are taken to a fake Amazon website where the recipient is informed that if they fill out a short survey, they will be given a change to receive a “Thank You” gift that is worth at least $100. As you can see in the image below, the web page looks and feels very much like the Amazon website.

Hikvision HikWire blog article Smishing part 2, image 2

After completing the survey and accepting the gift, How-To Geek states, “The real scam resides in the fine print. By agreeing to pay the small shipping fee, you’re also signing up for a 14-day trial to the company that sells the scammy products. After the trial period, you will be billed $98.95 every month and sent a new supply of whatever item you claimed as a reward.”

Hikvision HikWire blog article Smishing part 2, image 3

Scams are not the only style of smishing. Just like traditional phishing, many smishing attacks are trying to trick the recipient into sharing sensitive information or login credentials.

As you can see in the image below, there are three smishing examples. A fake bank security text, a free data offer that is using the target’s name, and a social engineering attack in Facebook messenger.

Hikvision HikWire blog article Smishing part 2, image 4

And, when you click or tap on the smishing link, you may be directed to a page that looks almost exactly like the valid website. You can see in the image below, there is little difference between the fake page and real page.

Hikvision HikWire blog article Smishing part 2, image 5

Five Tips to Identify and Protect Against Smishing
While it is more difficult to identify some smishing attacks versus a phishing email, there are some things that you can do. Below are five tips from Hikvision to identify and protect against smishing:

  1. Don’t respond to messages from phone numbers or accounts you are not familiar with.
     
  2. Check the phone number or code that sent the message. If it’s not familiar, look it up online and see if there are other reports of spam or smishing coming from that number.
     
  3. Often, a “smishing message will come from a ‘5000’ number instead of displaying an actual phone number. This usually indicates the text message was sent via email to the cell phone, and not sent from another cell phone,” shared Intuit.
     
  4. If you’re not expecting a message, be very cautious. If you place an order for food delivery and are instantly sent a text message with a link to check the status, it’s likely safe. If you receive a similar text message and did not place an order, be very cautious and log into the app or website directly to verify the order.
     
  5. If you’ve become the target of a smishing attack, How-to Geek recommends blocking the number immediately. iPhone and Android users both have access to built-in spam-blocking tools that should help cut down on the number of fake messages.

For more Hikvision insights to avoid hacks and reduce vulnerabilities, visit this link online.

IMPORTANT! This model requires non-standard firmware. Do Not Install standard firmware (e.g. v.4.1.xx) on this model. Doing so will permanently damage your system. You must use custom firmware v.4.1.25 from the iDS-9632NXI-I8/16S product page.

View the most updated version of this document here:

https://techsupportca.freshdesk.com/en/support/solutions/articles/17000113531-i-series-nvr-firmware-upgrade-instructions

 

The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.

 

Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.

 

After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.

 

Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.

 

Upgrading from v3.4.92 build 170518 or Older

  1. All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
  2. If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
  3. After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
  4. After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
  5. To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
  6. If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.

 

Upgrading from Any v4.X Build to v4.50.00.

  1. Any v4.X build can be upgraded directly to v4.50.00.
  2. Export configuration is highly recommended before performing the upgrade.
  3. If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.

 

Downgrading

Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience. 
 


Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.
 


Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.

 

Action after firmware upgraded 

1. Upgrade the DVR according to the chart above. 

2. Reconfirming Channel's Recording Schedule 

    - Confirm channel's recording schedule is enable. 

    - Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

    - Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode. 

4. Perform Database Rebuild locally. 

    • Some version above support Database Rebuild via web access - K51 and K72

    • Perform Database Rebuild regardless if system is having any database issue symptom. 

    • Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

    • After Database Rebuild - Check log to confirm Database Rebuild has went thru properly. 

    • If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

    • To check log > System > Log > Information > Database Rebuild Started and Stopped.

    • If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process. 

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.

 

 

 

 

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the DS-76xxNI-Q1(2)/P NVRs, also known as “Q series.”

 

These changes do not have any effect on the performance, specifications, or the user interface of the NVRs. For the ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

 

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

 

  • The C-Version NVRs must use firmware version v4.31.102 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v4.30.085 or older.

 

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the Value Express Series NVRs

These changes do not have any effect on the performance and specification of the recorders. For ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

  • The C-Version NVRs must use firmware version v4.30.216 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v3.4.104 or older.

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

By downloading and using software and other materials available via this website, you agree to be legally bound by HIKVISION General Terms of Use . If you don’t agree to these terms, you may not download or use any of those materials.

If you are agreeing on behalf of your company, you represent and warrant that you have legal authority to bind your company to the General Terms of Use above. Also you represent and warrant that you are of the legal age of majority in the jurisdiction in which you reside (at least 18 years of age in many countries).