Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

DPRK Fake Construction Front: Three Contractor Checks

A DPRK fake construction company case tests contractor verification through conflicting records and a video call. Use three checks before approval.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
21 November 2026
Reading time
6 min read
A construction plan and video frame meet at a supplier verification gate

A DPRK fake construction company can look credible through a website, a local address, and a live video call. On November 19, 2026, Silent Push described one suspected front that approached construction and engineering contracts. Its researchers tested the operator in two calls and reported signs of real-time face manipulation during the second.

The case is a test of contractor verification, not a confirmed contract loss. Silent Push assessed the operator as a North Korean remote worker, based on registration data and the calls. It did not document an awarded contract or a harmed customer. Buyers should therefore use the case to test their approval process without treating every unusual video call as proof of the same actor.

What Is a DPRK Fake Construction Company in This Case?

Here, the phrase means a business identity that Silent Push assessed as a front for a North Korean operator seeking construction and engineering work. The site presented a US contractor, described design and building services, and claimed an established record. A prospective client could encounter a plausible supplier before any contract was signed.

Silent Push’s attribution has two stated supports. The site’s registration email appeared on a publicly reported list attributed to North Korean IT workers. The researchers also observed behavior during two calls that they considered consistent with a concealed identity. The email-list attribution comes from another researcher, and the call behavior supports suspicion rather than independently proving nationality.

The researchers compare the tradecraft with earlier fake-company operations aimed at developers. That comparison does not establish that this construction front was run by Contagious Interview, Famous Chollima, or WageMole. It identifies a similar method: a durable business facade and a persona that survives initial contact. The reported goal in this case was to seek contracts directly.

Where Did the Contractor Identity Fail Verification?

The first failure was in business records. Silent Push found that the phone number shown on the site differed from its telephone link and from the domain registration. The listed location also conflicted with registration details. Those mismatches matter because a third-party risk management platform review must compare the visible contact page with the underlying record.

The second failure was in the claimed history. The site claimed more than ten years in business, while Silent Push dated its domain registration to October 18, 2025. A newer domain does not by itself prove a company is false. It creates a question that the supplier should answer with independent company and project records.

The third failure emerged when the researchers asked to verify the representative. During a first call of about 25 minutes, the operator kept the camera off, according to Silent Push. He resisted identity verification and agreed to use video on a second call. This sequence shows how an apparent sales conversation can move toward a contract without clearing the person’s identity.

Three verification points in the reported case
Three verification points in the reported caseAttack path in 4 steps: 1, Contractor site (Facade), then claims an established business; 2, Contact and registration (Records), then details conflict; 3, First and second calls (Call), then identity check meets resistance; 4, Independent verification (Decision).FacadeRecordsCallDecisionclaims an established…details conflictidentity check meets…ContractorsiteContact andregistrationFirst andsecond callsIndependentverification
  1. Contractor siteFacadeclaims an established business
  2. Contact and registrationRecordsdetails conflict
  3. First and second callsCallidentity check meets resistance
  4. Independent verificationDecision

This diagram maps the reported observations to an approval decision. It is our verification workflow, not a claim that a buyer completed these checks in the case. Each point asks for evidence from a different channel before a team grants supplier access or commits work.

What Did the Two Calls Actually Show?

Silent Push arranged the calls while posing as a prospective client. In the first, the operator spoke with the camera off. The researchers raised identity verification, met resistance, and obtained agreement to turn on the camera next time. The report does not give separate calendar dates for those calls.

In the second call, the researchers reported visible layering artifacts and facial distortion after the camera came on. They said the operator kept his mouth partly out of frame. When asked to lean back, he exposed more of his face, which made the anomalies easier to see. Silent Push interpreted these signs as real-time deepfake use.

The researchers then asked the operator to place a hand in front of his face. Silent Push says he declined and ended the video feed soon afterward. A refusal is a reason to slow verification; it is not a standalone identity finding. A poor connection or ordinary camera issue can also distort video, so the record checks remain essential.

The deepfake definition explains the synthetic-media concept behind this visual test. The deepfake fraud response guide provides a separate response path if an organization has already relied on a suspicious call. Neither page replaces independent contractor checks.

How Should a Buyer Decide Whether to Proceed?

Start with an independent record match before treating a polished site as evidence of a real contractor. Compare the stated legal business identity, address, phone numbers, and operating history with records obtained outside the supplier’s links. Silent Push recommends checking construction licenses with the relevant state licensing board directly.

Next, verify the representative through a channel that the applicant did not provide during the same call. If a call contains facial artifacts, ask for a clearer view and pause the approval when the person refuses. Record the result as an unresolved identity question. Avoid calling a visual artifact definitive evidence of nationality or software use.

Finally, separate supplier approval from technical access. A procurement owner should document which record was checked, which identity remains unverified, and who can resolve the discrepancy. Document that decision before the supplier receives a purchase order, sensitive plans, or system access.

These checks are our operational reading of Silent Push’s case and its verification advice. A failed check should trigger a documented follow-up, not an automatic accusation. Teams can ask for an alternate contact, licensing-board record, or in-person verification appropriate to the work before making a decision.

What Does This Evidence Establish?

Silent Push documented one alleged front and its own two-call test. Its report supports the observed discrepancies, the researchers’ deepfake assessment, and their stated DPRK attribution. It does not establish that the front won a construction contract, entered a customer’s environment, or caused a verified loss. Earlier malware campaigns described in the report should not be imported into this case.

Brandefense Blackhole counted 69 dark-chat posts matching the broad term “DPRK” from August 23 through November 21, 2026. The unit is matching posts, not unique people or incidents. This broad count does not tie the chat to the construction front or validate Silent Push’s attribution. It adds context for ongoing discussion, not evidence of a contract outcome.

The practical conclusion is narrow: a credible website and video presence are insufficient contractor checks. The three decision points are business records, the representative’s identity, and a documented approval gate. Silent Push’s case shows why teams need all three before a supplier relationship advances.

Frequently Asked Questions

Did the reported front win a construction contract?

Silent Push described an effort to seek construction and engineering work. Its report does not document an awarded contract or a verified customer loss.

Does a suspicious video call prove the representative used a deepfake?

Silent Push interpreted layering and facial distortion in its second call as deepfake indicators. A buyer should combine call observations with independent identity and business checks.

What should procurement verify before approving a contractor?

Check business and contact records, operating history, relevant licenses, and the representative's identity through independent channels. Document unresolved differences before approving work or access.

Sources

  1. Silent Push, Silent Push Exposes North Korean Fake Construction Company, November 19, 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →