bodyType

customContents

entityId

printArticlePageQuery

filter

article

body

urlAlias

articleSectionsContent

articleSeoArticle

articleSourceHeaderArticle

contentSchemaRenderContent

contentSubHeadlineContent

contentHeadlineContent

mainImagePrintArticleArticle

authorBlockPrintArticleArticle

contentSponsorTagContent

articlePianoPaywallContent

scmpYoutubeContent

hooksTrackPageViewArticle

query printArticlePageQuery(
  $entityId: String!
  $customContents: [CustomContentInput]
  $bodyType: BodyFormatTypeEnum
) {
  article(filter: {entityId: $entityId}) {
    entityId
    body(customContents: $customContents, type: $bodyType) {
      json
    }
    urlAlias
    ...articleSectionsContent
    ...articleSeoArticle_3o8td4
    ...articleSourceHeaderArticle
    ...contentSchemaRenderContent
    ...contentSubHeadlineContent
    ...contentHeadlineContent
    ...mainImagePrintArticleArticle
    ...authorBlockPrintArticleArticle
    ...contentSponsorTagContent
    ...articlePianoPaywallContent
    ...scmpYoutubeContent
    ...hooksTrackPageViewArticle
    id
  }
}

fragment articlePianoPaywallContent on Content {
  __isContent: __typename
  ...hooksPaywallPromiseContent
}

fragment articleSectionsContent on Content {
  __isContent: __typename
  sections {
    value {
      ...helpersCheckIfNewsSectionInFirstIndexSection
      ...entityLink
      name
      id
    }
  }
}

fragment articleSeoArticle_3o8td4 on Article {
  ...hooksArticleSeoArticle
  ...helpersCheckIsPostiesArticle
  ...helpersGetArticleTypeArticle
  entityId
  publishedDate
  updatedDate
  summary {
    text
  }
  subHeadline {
    text
  }
  body(customContents: $customContents, type: $bodyType) {
    text
  }
  keywords
  sections {
    value {
      name
      id
    }
  }
  topics {
    name
    entityId
    id
  }
  urlAlias
  authors {
    name
    id
  }
  images {
    style(filter: {style: "768x768"}) {
      url
    }
  }
  readingTime
}

fragment articleSourceHeaderArticle on Article {
  urlAlias
  ...entityLink
}

fragment authorBlockPrintArticleArticle on Article {
  ...defaultArticleDateContent
  ...authorNamesArticle
}

fragment authorNameAuthor on Author {
  ...entityLink
  name
  entityUuid
}

fragment authorNamesArticle on Article {
  authorLocations
  authors {
    entityId
    location
    ...authorNameAuthor
    id
  }
}

fragment blockquoteQuoteContent on Content {
  __isContent: __typename
  ...contentShareWidgetContent
}

fragment checkersCheckContentContainsStarlingImageContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment contentHeadlineContent on Content {
  __isContent: __typename
  headline
  socialHeadline
  ...contentHeadlineTagContent
  ...helpersUseContentSponsorContent
}

fragment contentHeadlineTagContent on Content {
  __isContent: __typename
  ...hooksContentHeadlineTagContent
}

fragment contentNewsletterWidgetContent on Content {
  __isContent: __typename
  topics {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
    id
  }
  sections {
    value {
      relatedNewsletters {
        ...helpersMassageToNewsletterItemNewsletter
        id
      }
      id
    }
  }
  ... on Article {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
  }
}

fragment contentSchemaRenderContent on Content {
  __isContent: __typename
  ...blockquoteQuoteContent
  ...imageContent
  ...inlineWidgetContent
  ...photoGalleryWidgetContent
  ...scmpYoutubeContent
}

fragment contentShareWidgetContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  shortUrl
  socialHeadline
  headline
}

fragment contentSponsorTagContent on Content {
  __isContent: __typename
  ...helpersUseContentSponsorContent
}

fragment contentSubHeadlineContent on Content {
  __isContent: __typename
  subHeadline {
    json
  }
  summary {
    json
  }
  ...contentSchemaRenderContent
}

fragment defaultArticleDateContent on Content {
  __isContent: __typename
  ...hooksArticleDateUtilsContent
}

fragment entityLink on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  __typename
  entityId
  entityUuid
  urlAlias
  urlRedirect {
    toUrl
    id
  }
  application {
    entityId
    id
  }
  ... on Section {
    fullSectionPath {
      entityId
      id
    }
    parentSection
  }
  ...helpersAppBarVariantBase
  ...helpersApplicationBase
  ...helpersCheckIsPlusArticle
  ...helpersStyleSectionContent
}

fragment helpersAppBarVariantBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsLiveArticle
  ...helpersCheckIsPlusPage
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...helpersSectionContent
  ...helpersStyleSectionContent
}

fragment helpersApplicationBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPlusPage
}

fragment helpersCheckIfNewsSectionInFirstIndexSection on Section {
  name
}

fragment helpersCheckIsAmpEnabledArticle on Article {
  entityId
  types {
    value {
      entityId
      id
    }
  }
  sections {
    value {
      entityId
      id
    }
  }
  disableOffPlatformContent
  sponsorType
  published
  ...helpersCheckIsPlusArticle
  ...helpersCheckIsPostiesArticle
}

fragment helpersCheckIsLiveArticle on Article {
  flattenTypeIds
  liveArticle {
    status
    id
  }
}

fragment helpersCheckIsMainTopicContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment helpersCheckIsPlusArticle on Content {
  __isContent: __typename
  ... on Article {
    paywallTypes {
      entityUuid
      id
    }
  }
}

fragment helpersCheckIsPlusPage on Page {
  urlAlias
}

fragment helpersCheckIsPostMagazineArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesPage on Page {
  urlAlias
}

fragment helpersCheckIsStyleArticle on Content {
  __isContent: __typename
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersGetArticleTypeArticle on Content {
  __isContent: __typename
  ... on Article {
    types {
      value {
        entityId
        id
      }
    }
  }
}

fragment helpersMassageToNewsletterItemNewsletter on Newsletter {
  entityId
  name
  alternativeName
  description {
    text
  }
  summary {
    text
  }
  homepageDescription {
    text
  }
}

fragment helpersSanitizeArticleTypeEntityIdsArticle on Article {
  types {
    value {
      entityId
      id
    }
  }
}

fragment helpersSanitizeAuthorTypesArticle on Article {
  authors {
    types
    id
  }
}

fragment helpersSanitizedAuthorEntityIdsArticle on Article {
  authors {
    entityId
    id
  }
}

fragment helpersSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersStyleSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersUseContentSponsorContent on Content {
  __isContent: __typename
  topics {
    entityId
    sponsor {
      ...sponsorTagSponsor
      name
      type
      id
    }
    id
  }
  ... on Article {
    sponsorType
  }
  ...helpersCheckIsMainTopicContent
}

fragment hooksArticleDateUtilsContent on Content {
  __isContent: __typename
  createdDate
  publishedDate
  updatedDate
}

fragment hooksArticleSeoArticle on Article {
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...hooksContentHeadlineTagContent
  ...helpersCheckIsAmpEnabledArticle
  entityId
  headline
  socialHeadline
  types {
    value {
      entityId
      id
    }
  }
  authors {
    entityId
    id
  }
  images {
    generic_og: style(filter: {style: "og_image_scmp_generic"}) {
      url
    }
    styles(filter: {styles: ["og_image_posties_article", "og_postmag", "og_image_style", "og_image_scmp_analysis", "og_image_scmp_explainer", "og_image_scmp_editorial", "og_image_scmp_fact_check", "og_image_scmp_debate", "og_image_scmp_live", "og_image_scmp_obituary", "og_image_scmp_opinion", "og_image_scmp_review", "og_image_scmp_series", "og_image_scmp_generic"]}) {
      url
      style
    }
    type
  }
  urlAlias
}

fragment hooksContentHeadlineTagContent on Content {
  __isContent: __typename
  __typename
  ... on Article {
    types {
      value {
        name
        entityId
        description {
          text
        }
        id
      }
    }
    ...helpersCheckIsStyleArticle
  }
  flag
  sections {
    value {
      name
      id
    }
  }
  ...hooksContentHelperContent
}

fragment hooksContentHelperContent on Content {
  __isContent: __typename
  ...helpersSanitizeArticleTypeEntityIdsArticle
  ...helpersSanitizeAuthorTypesArticle
  ...helpersSanitizedAuthorEntityIdsArticle
  flag
}

fragment hooksPaywallPromiseContent on Content {
  __isContent: __typename
  entityId
  ...helpersCheckIsPostiesArticle
}

fragment hooksTrackPageViewArticle on Article {
  entityId
  publishedDate
  headline
  sections {
    value {
      name
      id
    }
  }
  urlAlias
  authors {
    name
    id
  }
  entityUuid
}

fragment imageContent on Content {
  __isContent: __typename
  headline
  ...checkersCheckContentContainsStarlingImageContent
}

fragment inlineWidgetContent on Content {
  __isContent: __typename
  ...contentNewsletterWidgetContent
}

fragment mainImagePrintArticleArticle on Article {
  images {
    title
    url
    isSlideshow
    size_652x446: style(filter: {style: "652x446"}) {
      url
    }
  }
}

fragment photoGalleryDialogContent on Content {
  __isContent: __typename
  __typename
  ...contentShareWidgetContent
}

fragment photoGalleryWidgetContent on Content {
  __isContent: __typename
  ...photoGalleryDialogContent
}

fragment scmpYoutubeContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  publishedDate
}

fragment sponsorTagSponsor on Sponsor {
  name
  type
  images {
    url
  }
}


sections

types

disableOffPlatformContent

sponsorType

published

headline

socialHeadline

authors

images

publishedDate

updatedDate

summary

subHeadline

keywords

topics

readingTime

authorLocations

entityUuid

Ann Cao

Tracy Qu

Premier Li Keqiang stressed the importance of information security at a State Council meeting on Wednesday, a message that has taken on new urgency in the wake of an alleged data leak of 1 billion Chinese residents.
Chinese government bodies must “defend information security … to protect personal information, privacy and confidential corporate information” so people can feel secure when submitting data for certain public services, according to a statement summarising the cabinet meeting.
The statement did not mention specific security issues or the alleged data leak.
The main topic of the meeting was “digital government development”, a general term referring to Beijing’s plan to leverage technologies like big data and artificial intelligence for social governance and public services. The line about security did not come until the end of the statement, but securing data has become an increasingly important priority for the government, especially since the enactment of two related laws last year.
Tax scammers hack government-run facial recognition system
Li’s comments come after a data set allegedly containing the information of 1 billion Chinese residents appeared last week on the hacker community Breach Forum. The poster, using the handle “ChinaDan”, said the data included names, addresses, identification numbers and mobile phone numbers. The person was charging 10 bitcoin, or about US$200,000, for the full data set.
In the forum post, the data was said to be taken from a database managed by Shanghai police. If confirmed, the leak could be the largest-ever personal data security breach in the country.
Forum administrators have since removed the post. The South China Morning Post was unable to verify the authenticity of the data, and no government officials in China have responded to the alleged leak. When reached by phone, Shanghai police did not respond to a request for comment.
Cybersecurity experts told The Wall Street Journal that the data was exposed to the web through a dashboard used to access that data without a password. They said the total size of the information came in at 23 terabytes, corroborating claims from the original post.
The size of the alleged hack has triggered concerns about its implications at a time when China’s state apparatus is collecting huge swathes of data from its citizens for social surveillance and governance.


After the claimed leak, Chinese social media platforms sprang into action, censoring related content.
The information could be “the largest data leak of its kind in China”, causing a “permanent negative experience”, said Zhao Xuan, a cybersecurity lawyer at Beijing Bairui Law Firm.
“China has 1.4 billion people. The seller claimed to include the data of 1 billion, and considering it was leaked from the police database, the quantity and quality of the data could be quite high,” Zhao added.
A sample data set in the form of three JavaScript Object Notation-format files containing 560 megabytes of information included fields for names, birth dates, addresses, mobile phone numbers, personal identification numbers, photos, and even ethnicities.
At the same time, a number of users have questioned the authenticity of the leak.
“Seems like an advanced scam,” a person going by the name “Victim” responded to the post on the forum, adding that the domain used in the URLs for photos in the database redirects to a UK-based domain registration site. Another user on Twitter argued that the sample sets could have been cobbled together from previously available semi-public data.
China’s GDS sees Singapore as hub for Southeast Asian data centres
The case highlights problems facing data security in China even as the central government has sought to enhance protections for personal information over the past year. Last November, the Personal Information Protection Law took effect, giving China some of the world’s toughest rules for personal data security by placing restrictions on how data on internet users can be collected, used and managed.
The law is set to make it significantly harder and more expensive for tech firms in China to access and use consumer information, with a broad impact that is being compared to the implementation of the European Union’s General Data Protection Regulation.
Zhao said those responsible for the leak and hacking could be charged under China’s criminal law, which would include charges for infringing on citizens’ personal information and illegally accessing computer information systems.
Chinese authorities have previously said the country is a consistent target of overseas hackers. Northwestern Polytechnical University, one of the country’s top schools for national defence research, said in a statement last month that it was the target of a cyberattack from overseas hackers.
China says the US is an ‘empire of hacking’ following NSA advisory
At home, the country is also subject to constant data leaks and has a rampant underground market for personal information. In 2020 alone, China investigated 560,000 cases of cybercrime and arrested over 80,000 suspects, including 13,000 suspects involved in personal information infringement and another 2,975 suspects involved in hacking, according to the Ministry of Public Security.
As the latest alleged data leak picked up steam online, Tencent Holdings and Weibo started censoring related posts. One commentary on Tencent’s WeChat that claimed the leak will bring “permanent, implacable influences” disappeared soon after being published. On Weibo, a microblogging platform, related content under the topic “Shanghai national police database” was cleared out.
Data leaks are becoming a bigger issue for countries around the world. Earlier this year, the personal data of 22.5 million Malaysian citizens – including full names, ID numbers, photos, home addresses and phone numbers – were stolen from government servers and sold on the dark web for a reported price of US$10,000. Soon after, Malaysian computer security experts discovered a website offering access to a wide range of personal data on the country’s citizens.
https://www.scmp.com/week-asia/article/3183878/why-malaysia-seeing-rise-data-leaks-and-what-government-doing-stop-it


China premier stresses data security after alleged leak affecting 1 billion Chinese residents triggers concerns

A person on a hacker forum claimed to be selling data on 1 billion Chinese citizens stolen from Shanghai police servers. The size of the leak spurred online discussions that were quickly censored. Photo: Shutterstock

Tech

Big Tech

Policy

Tech Trends

Business

China Business

News

China

Money & Wealth

Premier Li Keqiang called on government bodies to ‘defend information security’, which has become a rising concern as authorities collect more citizen data
The comments come after what could be the largest ever data leak for China, with data sets showing names, birth dates, ID numbers and other sensitive information


Premier Li Keqiang called on government bodies to ‘defend information security’ after the appearance online of what could be the largest-ever data leak in China.


Cybersecurity

China technology