{"schema_version":"0.8.0","id":"LR-2026-0106","record_version":4,"title":"Bee Cheng Hiang mass marketing e-mail exposes 95,000 customer addresses after AI-generated code omitted recipient hiding","verification":{"human_verified":false,"method":"automated_gate","auto_verified":true,"score":54.8,"score_breakdown":{"source_authority":12.1,"independent_corroboration":7.0,"implicated_party_confirmed":0.0,"citation_integrity":14.0,"specificity":6.0,"completeness":8.0,"unhedged_language":5.0},"checks":{"schema_valid":true,"every_field_cited":true,"quotes_verbatim":true,"source_fetched":true,"distinct_incident":true,"dates_plausible":true,"sources_agree":true},"gate_version":"gate-2026-09-29.5","cross_check_model":null,"cross_check_agreement":null,"duplicate_of":null,"verified_by":null,"verified_at":"2026-09-30","extraction_run_id":null},"system":{"model_name":"unknown","model_version":null,"developer":"unknown","harness":null,"tools_granted":[],"permissions_scope":null,"autonomy_level":"unknown","guardrails_present":[],"deployment_context":"production","tier":null,"lifecycle_stage":"production","integration_type":"embedded","intended_use":"to write a program to send a “mass e-mail using a local list” in batches","safeguard_state":"The commission said the AI tool had not malfunctioned.","production_intended":true},"event":{"date_occurred":"2026-04-25","date_disclosed":"2026-09-30","incident_class":"privacy_leakage","failure_class":null,"agent_involved":false,"secondary_failure_classes":[],"trigger":"unknown","duration":null,"detection_method":"human_review","summary":"Bee Cheng Hiang, a Singapore food company, used an AI tool for the first time to write code for sending marketing e-mails in batches from a local customer list. The prompt omitted instructions to hide recipients’ addresses, so the code sent e-mails on Apr 25 with all addresses visible to every recipient, exposing more than 95,000 customers’ e-mail addresses. The company discovered and confirmed the error, stopped the mass distribution, rectified the code and notified affected customers; PDPC was notified on Apr 27. PDPC accepted a voluntary undertaking on Sep 2, and the company added double-verification checks and an AI governance framework.","tags":["ai-generated-code","email-address-exposure","mass-email","data-protection-act"],"date_detected":null,"near_miss":false,"root_cause":null,"root_cause_detail":null,"failure_class_detail":"No autonomous agent was involved; the harm came from code the employee generated with an AI tool and deployed without adequate review.","responsible_party":null,"adversarial_actor":null,"input_provenance":null,"time_to_contain":null,"operations_paused":null,"remediation":"Since the incident, the company has implemented “double-verification checks” by at least two staff members for all bulk e-mail communications before sending them.","precursor_events":null,"control_failure":[{"element_id":"C05","state":"absent","quote":"It added that the company had relied on a single employee “without a review process for supervisory checks of the employee’s work, and did not have a governance framework or policies in place to guide employees on the use of generative AI tools for work”.","source_index":0}]},"impact":{"direct_loss_usd":null,"remediation_hours":null,"records_exposed":null,"third_parties_affected_count":null,"severity":"moderate","severity_because":"moderate, because data or systems of others touched, with a bounded scope stated: More than 95,000 customers’ e-mail addresses were exposed to other recipients, a bounded scope of personal data of others.","harm_class":["privacy"],"affected_description":"More than 95,000 of Bee Cheng Hiang’s customers whose e-mail addresses were exposed","protected_class_involved":null,"data_categories_exposed":["pii"],"loss_range_usd":null,"reversibility":null,"downstream_exposure_count":null},"evidence":{"sources":[{"url":"https://www.businesstimes.com.sg/singapore/bee-cheng-hiang-customers-e-mail-addresses-exposed-singapores-first-case-ai-related-data-breach","publisher":"news search (Bing News index)","date":"2026-09-30","type":"press","title":"Bee Cheng Hiang customers’ e-mail addresses exposed in Singapore’s first case of AI-related data breach","archived_url":null,"attachment":"first_report"},{"url":"https://e.vnexpress.net/news/tech/tech-news/emails-of-95-000-customers-exposed-in-singapore-s-first-ai-related-data-breach-5127451.html","publisher":"news search (Google News index)","date":"2026-10-04","type":"press","title":"Emails of 95,000 customers exposed in Singapore's first AI-related data breach - VnExpress International","archived_url":null,"attachment":"first_report"}],"per_field_confidence":{"system.model_name":"D","system.lifecycle_stage":"D","system.integration_type":"D","system.intended_use":"C","system.production_intended":"D","system.developer":"D","system.deployment_context":"D","system.autonomy_level":"D","event.date_occurred":"C","event.near_miss":"D","event.remediation":"D","event.agent_involved":"D","event.detection_method":"D","event.summary":"D","event.incident_class":"D","event.date_disclosed":"A","event.trigger":"D","impact.harm_class":"D","impact.affected_description":"C","impact.data_categories_exposed":"D","impact.severity":"D","context.industry":"D","context.regulatory":"C","context.denominator_available":"D","context.country":"C","event.failure_class_detail":"D","impact.severity_because":"D","event.control_failure":"C","system.safeguard_state":"C","event.tags":"D"},"field_citations":{"system.model_name":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."}],"system.developer":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"The employee asked the AI tool to write a program to send a \"mass email using a local list\" in batches, but did not instruct it to hide recipients' email addresses from one another."}],"system.deployment_context":[{"source_index":0,"quote":"The problematic marketing e-mails were sent out on Apr 25, and PDPC was notified of the data breach on Apr 27."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"system.lifecycle_stage":[{"source_index":0,"quote":"The problematic marketing e-mails were sent out on Apr 25, and PDPC was notified of the data breach on Apr 27."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"system.integration_type":[{"source_index":0,"quote":"It was also the first time the home-grown traditional food products company known for its bak kwa was using an AI tool for its business operations."},{"source_index":1,"quote":"The employee asked the AI tool to write a program to send a \"mass email using a local list\" in batches, but did not instruct it to hide recipients' email addresses from one another."}],"system.intended_use":[{"source_index":0,"quote":"Rather, the issue was with the prompt the employee gave the tool to write a program to send a “mass e-mail using a local list” in batches, but without specific instructions to hide the e-mail address of each recipient from other customers."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"system.production_intended":[{"source_index":0,"quote":"It was also the first time the home-grown traditional food products company known for its bak kwa was using an AI tool for its business operations."}],"system.autonomy_level":[{"source_index":0,"quote":"“The incident was caused by a human error in developing the e-mail distribution code with an AI tool,” PDPC told ST."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"event.date_occurred":[{"source_index":0,"quote":"The problematic marketing e-mails were sent out on Apr 25, and PDPC was notified of the data breach on Apr 27."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"event.detection_method":[{"source_index":0,"quote":"After the company discovered and confirmed the error, it stopped the mass distribution of the e-mails, rectified the bad code and notified all affected customers, PDPC said."}],"event.summary":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"event.incident_class":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"event.agent_involved":[{"source_index":0,"quote":"“The incident was caused by a human error in developing the e-mail distribution code with an AI tool,” PDPC told ST."},{"source_index":1,"quote":"The employee asked the AI tool to write a program to send a \"mass email using a local list\" in batches, but did not instruct it to hide recipients' email addresses from one another."}],"event.failure_class_detail":[{"source_index":0,"quote":"“The incident was caused by a human error in developing the e-mail distribution code with an AI tool,” PDPC told ST."}],"event.near_miss":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"event.remediation":[{"source_index":0,"quote":"Since the incident, the company has implemented “double-verification checks” by at least two staff members for all bulk e-mail communications before sending them."}],"impact.harm_class":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."}],"impact.affected_description":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"impact.data_categories_exposed":[{"source_index":0,"quote":"These customer e-mail addresses were the only personal data affected, and they were not managed, processed or generated by any AI-powered operation or process, the commission said."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"impact.severity_because":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"context.industry":[{"source_index":0,"quote":"It was also the first time the home-grown traditional food products company known for its bak kwa was using an AI tool for its business operations."},{"source_index":1,"quote":"| A Bee Cheng Hiang outlet in Singapore. Photo from Bee Cheng Hiang's Facebook |"}],"context.country":[{"source_index":0,"quote":"[SINGAPORE] More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."}],"context.regulatory":[{"source_index":0,"quote":"Considering the circumstances of the case, the commission accepted a voluntary undertaking by Bee Cheng Hiang on Sep 2 to improve its compliance with the Personal Data Protection Act."},{"source_index":1,"quote":"The PDPC accepted a voluntary undertaking from the company on Sept. 2 to improve its compliance with Singapore's Personal Data Protection Act, according to Channel News Asia."}],"impact.severity":[{"source_index":0,"quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach."},{"source_index":1,"quote":"Only customers' email addresses were exposed, and there was no evidence they were subsequently misused, the regulator said."}],"event.date_disclosed":[{"source_index":0,"quote":"published: 2026-09-30"},{"source_index":1,"quote":"published: 2026-10-04"}],"event.control_failure":[{"source_index":0,"quote":"It added that the company had relied on a single employee “without a review process for supervisory checks of the employee’s work, and did not have a governance framework or policies in place to guide employees on the use of generative AI tools for work”."},{"source_index":1,"quote":"The PDPC found that Bee Cheng Hiang had not sufficiently tested the AI-generated code and lacked supervisory checks and policies governing employees' use of generative AI."},{"source_index":1,"quote":"During testing, the employee checked activity logs but did not review an actual test email, allowing the error to go unnoticed."}],"system.safeguard_state":[{"source_index":1,"quote":"The commission said the AI tool had not malfunctioned."}],"event.tags":[{"source_index":1,"quote":"The breach occurred on April 25 after an employee used a generative artificial intelligence tool to create a Python script for sending marketing emails, according to Singapore's Personal Data Protection Commission (PDPC)."},{"source_index":1,"quote":"The resulting code sent emails to batches of about 1,000 customers, with recipients' addresses visible to others in the same batch."},{"source_index":1,"quote":"The PDPC accepted a voluntary undertaking from the company on Sept. 2 to improve its compliance with Singapore's Personal Data Protection Act, according to Channel News Asia."}]},"notes_on_gaps":"No source states the AI tool's model name, version, developer, harness, tools granted, permissions scope, or the human-in-the-loop arrangement during the code generation, so system.model_name, system.model_version, system.developer, system.harness, system.tools_granted, system.permissions_scope and system.autonomy_level are unknown. No source states a monetary loss figure, remediation hours, third-party affected count, loss range, reversibility, downstream exposure count, org size band, denominator, systemic exposure, shared model id, upstream incident id, incident evidence integrity, coverage posture, or precursor events. event.trigger is written as human_misuse from PDPC's statement that the incident was caused by human error in developing the code with an AI tool; the source does not state the employee intended harm, so this is the closest stated cause. event.root_cause is written as oversight because PDPC states the company relied on a single employee without a review process for supervisory checks; the absence of a governance framework is noted here as a gap rather than coded as a failed guardrail. event.detection_method is human_review because the company discovered and confirmed the error itself. event.date_detected is not written in fields per the pipeline rule; the source states PDPC was notified on Apr 27, which is a notification, not necessarily first detection. event.failure_class is null because no autonomous agent was involved. event.secondary_failure_classes is empty. impact.third_parties_affected_count is null because no source states a count of third parties affected, only records exposed. impact.direct_loss_usd is null because no source states a figure. context.denominator_available is false and context.denominator is null because no denominator is stated. context.systemic_exposure is null because no source states one shared model or component correlating loss across deployers. context.regulatory is written from the PDPC voluntary undertaking and the PDPA fine ceiling; litigation_status is unknown because no source states litigation. context.coverage is null because no source states insurance lines or posture. event.operations_paused is null because no source states a pause duration. event.precursor_events is null because no source describes earlier related events. event.input_provenance is null because no untrusted input carried an injection. event.adversarial_actor is none because no attacker is stated. event.responsible_party is deployer because the operator's employee developed and deployed the code. event.date_disclosed is written as 2026-09-30 from the source's statement that the commission told The Straits Times on Wednesday (Sep 30). event.trigger: human_misuse was classified, not stated; a trigger is never inferred, so it is unknown. event.root_cause: the stated reason names an absence, not a failed control: The commission said that the incident likely happened as Bee Cheng Hiang did not conduct sufficiently robust tests to check the e-mail distribution code before it was deployed. system.tier: not set; no operator named and deployment_context is not a lab's. [aggregated by deepseek-chat, aggregate-2026-09-27.1, 2026-10-01] system.model_name: classified from described behaviour. system.lifecycle_stage: production. system.integration_type: classified from described behaviour. system.production_intended: classified from described behaviour. system.developer: no source names the developer. system.deployment_context: production. system.autonomy_level: no source states the arrangement. event.near_miss: classified from described behaviour. event.remediation: classified from described behaviour. event.agent_involved: classified from described behaviour. event.detection_method: classified from described behaviour. event.summary: classified from described behaviour. event.incident_class: privacy_leakage. event.trigger: no source states a cause. impact.harm_class: privacy. impact.data_categories_exposed: classified from described behaviour. context.industry: classified from described behaviour. context.denominator_available: no denominator is available for this incident. [control failure inferred by deepseek-chat, controlfail-2026-10-11.2, 2026-10-11] Merged with LR-2026-0120, which described the same incident; their sources are included here. [corrected by Srini Iyer, approved 2026-10-18 in the corrections review: duplicate of another record, merged; source gives a bound, not an exact count]"},"context":{"industry":"Food Manufacturing","org_size_band":null,"country":"SG","denominator_available":false,"denominator":null,"related_incident_ids":[],"systemic_exposure":null,"shared_model_id":null,"upstream_incident_id":null,"incident_evidence":null,"regulatory":{"regimes":["PDPA"],"notifications":"PDPC was notified of the data breach on Apr 27.","litigation_status":"unknown","safety_policy_adherence":"PDPC accepted a voluntary undertaking by Bee Cheng Hiang on Sep 2 to improve its compliance with the Personal Data Protection Act."},"coverage":null},"narrative":{"steps":[{"step":"doing","text":"Bee Cheng Hiang, a Singapore food company, used an AI tool to write code for sending marketing e-mails in batches of 1,000 customers from a local list.","quote":"Rather, the issue was with the prompt the employee gave the tool to write a program to send a “mass e-mail using a local list” in batches, but without specific instructions to hide the e-mail address of each recipient from other customers.","source_index":0,"grade":"C"},{"step":"went_wrong","text":"The generated code sent marketing e-mails with all recipients’ addresses visible to everyone, exposing customer e-mail addresses instead of hiding them.","quote":"The bad prompt generated code that sent out marketing e-mails with all the recipients’ addresses visible to everyone.","source_index":0,"grade":"C"},{"step":"reached","text":"More than 95,000 customers’ e-mail addresses were exposed to other recipients; these addresses were the only personal data affected and there was no evidence of further misuse.","quote":"More than 95,000 of Bee Cheng Hiang’s customers had their e-mail addresses exposed in April after an employee used a bad prompt in an artificial intelligence tool, in Singapore’s first reported case of an AI-related data breach.","source_index":0,"grade":"C"},{"step":"caught","text":"The company discovered and confirmed the error itself, after the employee did not realise it before deploying the code; PDPC was notified on Apr 27.","quote":"After the company discovered and confirmed the error, it stopped the mass distribution of the e-mails, rectified the bad code and notified all affected customers, PDPC said.","source_index":0,"grade":"C"},{"step":"done","text":"The company stopped the mass distribution, rectified the code, notified all affected customers, and implemented double-verification checks by at least two staff for bulk e-mails, plus an AI governance framework and other measures.","quote":"After the company discovered and confirmed the error, it stopped the mass distribution of the e-mails, rectified the bad code and notified all affected customers, PDPC said.","source_index":0,"grade":"C"}],"model":"deepseek-chat","prompt_version":"aggregate-2026-09-27.1","extracted_at":"2026-10-01","source_urls":["https://www.businesstimes.com.sg/singapore/bee-cheng-hiang-customers-e-mail-addresses-exposed-singapores-first-case-ai-related-data-breach"]}}