Singapore Judgment

General Division of the High Court

Liew Cheong Wee Leslie v Public Prosecutor

On this page

Professional case brief

Research organized from the available case record

Source document

01

Holding and result

Court found from the evidence that the appellant deliberately obtained unauthorised remote access and executed commands causing the blackout, satisfying s3(1); however the prosecution failed to particularise or prove any 'damage' as defined in s2 required for s3(2), so the sixth charge could not stand as an s3(2) offence and must be treated as s3(1); convictions affirmed and sentences for the first five charges upheld; the sixth charge was amended to s3(1) and its sentence varied to a $3,000 fine (in default three weeks' imprisonment).

Court disposition

Convictions affirmed; appellant's appeal dismissed; sentences for first five charges upheld; sixth charge amended from s3(2) to s3(1) and sentence varied to a $3,000 fine (in default three weeks' imprisonment).

Orders

  • Appeal against conviction dismissed.
  • Appeal against sentences dismissed except as to the sixth charge.
  • Amend sixth charge by deleting reference to 'Section 3(2) read with' and treat as s3(1).
  • Vary sentence for sixth charge to a fine of $3,000 and in default three weeks' imprisonment.

02

Material facts

Parties

Liew Cheong Wee Leslie

Appellant Counsel: Wee Pan Lee (Wee Tay & Lim LLP)

Public Prosecutor

Respondent Counsel: Christopher Ong; Terence Chua (Attorney-General's Chambers)

Amounts and remedies

  • Number of Charges: 6
  • Fine Per Charge (charges 1 5): SGD 3,000
  • Original Sentence Sixth Charge Fine: SGD 15,000
  • Original Sentence Sixth Charge Imprisonment (weeks): 2
  • Varied Sixth Charge Fine: SGD 3,000
  • Varied Sixth Charge Default Imprisonment (weeks): 3

03

Procedural history

  1. Posture

    Magistrate's Appeal (criminal) / High Court Decision on Appeal

04

Questions and positions

Legal issues

Party arguments

Applicant
Applicant contended he was authorised to access the PMCS in his employment and was not a hacker; he relied on chain of command and his work on the MBS project and denied unlawful intent; he appealed convictions and sentences as excessive.
Respondent
Prosecution submitted appellant had no authority for the remote access he engineered, added a personal email to gain admin access, executed layered security commands deliberately causing a blackout; urged that the act amounted to intentional sabotage and that damage under s3(2) (including threat to public safety) was present and sentences should be substantially increased.

05

Court’s reasoning

  1. 01

    Computer Misuse Act (Cap 50A) s2

    Definition of 'damage' is specific and exhaustive under s2 of the Computer Misuse Act and must be particularised and proved

  2. 02

    Computer Misuse Act (Cap 50A) s3(1)-(2)

    Elements of the offence under s3(1) and the enhanced offence under s3(2) require proof of unauthorised access and, for s3(2), proof of damage as defined in s2

  3. 03

    Principle stated in judgment (prosecutorial duty/common law criminal procedure)

    Prosecution has duty to particularise the particulars constituting the charge so the accused can mount a defence

06

Ratio, limits and disposition

Ratio decidendi

Court found from the evidence that the appellant deliberately obtained unauthorised remote access and executed commands causing the blackout, satisfying s3(1); however the prosecution failed to particularise or prove any 'damage' as defined in s2 required for s3(2), so the sixth charge could not stand as an s3(2) offence and must be treated as s3(1); convictions affirmed and sentences for the first five charges upheld; the sixth charge was amended to s3(1) and its sentence varied to a $3,000 fine (in default three weeks' imprisonment).

Obiter and limits

  • Loss of reputation or commercial inconvenience is not 'damage' under s2
  • A blackout could amount to a threat to public safety as a common-sense proposition but must be alleged and proved at trial
  • Offences under s3 can vary widely in gravity; s3(2) will likely attract custodial sentences whereas s3(1) may or may not depending on seriousness

Court disposition

Convictions affirmed; appellant's appeal dismissed; sentences for first five charges upheld; sixth charge amended from s3(2) to s3(1) and sentence varied to a $3,000 fine (in default three weeks' imprisonment).

  • Appeal against conviction dismissed.
  • Appeal against sentences dismissed except as to the sixth charge.
  • Amend sixth charge by deleting reference to 'Section 3(2) read with' and treat as s3(1).
  • Vary sentence for sixth charge to a fine of $3,000 and in default three weeks' imprisonment.

Source and reliance status

General Division of the High Court · 25 July 2013

This page organises the available record for research. Confirm quotations, current status, and subsequent treatment against the official source before relying on the case.

Judgment reading view

Judgment text

The complete available source text.

Source document

General Division of the High Court

Judgment· 25 July 2013

[2013] SGHC 141

Liew Cheong Wee Leslie v Public Prosecutor [2013] SGHC 141 Case Number : Magistrate's Appeal No 91 of 2012 Decision Date : 25 July 2013 Tribunal/Court : High Court Coram : Choo Han Teck J Counsel Name(s) : Wee Pan Lee (Wee Tay & Lim LLP) for Leslie Liew Cheong Wee; Christopher Ong and Terence Chua (Attorney-General's Chambers) for the Public Prosecutor. Parties : Liew Cheong Wee Leslie — Public Prosecutor 25 July 2013 Choo Han Teck J: 1 The appellant was a 35-year-old engineer who was employed by Power Automation Pte Ltd (“PA”) from 17 January 2010. He left the company on 13 May 2010. At the time he was assigned to work in the Marina Bay Sands Integrated Resort in which PA was a sub-contractor for the setting up and installation of a “Power Monitoring Control System” or “PMCS”. It was a sophisticated computer system for managing and controlling all digitally controlled equipment in the resort including the casino. The trial judge summarised the description of the PMCS as – 8 The PMCS is a client/server system that collects status from field devices such as meters, circuit breakers, earth switches, battery chargers, UPS, network switches etc. The main supply system draws electricity from the national grid at 22kV. It is then distributed to all the sections of the site and stepped down to 400volts. The Circuit Control Switch Box to the casino is located in the gear room. The

switch controls the supply of electricity to the casino. 9 There are also 5 generators on site for the stand-by system which is rated at 6.6kV individually. The power generated by each generator goes into an individual transformer which stepped it up to 22kV. It is then distributed to all the sections of the site and it is stepped down to 400 volts by many transformers. This provides as an emergency backup power supply from the generator. These generators will operate in the event of power failure from the national grid. In the generator room, there is also a Switch Box which handles the power output. 10 All power will be supplied through a circuit-breaker. There are different circuit breakers for different circuits. Electricity will only flow if the circuit break is in the “closed” position. The circuit-breaker cuts off supply of electricity if it is in the “open” position. The breakers are installed with a local remote switch. If the switch was turned to local, the PMCS would not be able to control the breakers. If it was put on remote mode, the PMCS would be able [to] open or close the breakers. 11 The PMCS continuously monitors the status of the 22kV and 6.6kV electric distribution systems and automatically react to any power failure conditions. It allows the operator to use the Human Machine Interface (“HMI”) in any of the workstations to monitor and control the High

Tension (“HT”) system. It also allows the monitoring of the Low Voltage Main Switchboards. 12 The PMCS also maintain many records, known as logs. There is an entry log, and an alarm log. The entry log records the time, identity and action each time the PMCS is accessed. The alarm log records the alarms each time there is a malfunction. Access to the PMCS is by way of either the viewing account of Vicky or operator level OP1 with their respective passwords. 2 On 12 May 2010 there was a massive blackout at the casino around 12.20am. All levels from the basement to level 3 of the northern section of the casino were affected. The police were called because the security supervisor suspected that the blackout occurred because someone had wilfully tampered with the electrical system. After investigations, the appellant was charged on five counts under s 3(1) of the Computer Misuse Act (Cap 50A, 1998 Rev Ed) (“the Act”) and one count under s 3(2) of the Act. Sections 3(1) and (2) of the Act provide as follows – 3(1) Subject to subsection (2), any person who knowingly causes a computer to perform any function for the purpose of securing access without authority to any program or data held in any computer shall be guilty of an offence and shall be liable on conviction to a fine not exceeding $5,000 or to imprisonment for a term not exceeding 2 years or to both and, in the case of a

second or subsequent conviction, to a fine not exceeding $10,000 or to imprisonment for a term not exceeding 3 years or to both. (2) If any damage is caused as a result of an offence under this section, a person convicted of the offence shall be liable to a fine not exceeding $50,000 or to imprisonment for a term not exceeding 7 years or to both. He claimed trial and was eventually convicted by the court below on all six charges and was sentenced to a fine of $3,000 each for the first to fifth charges and two weeks imprisonment and $15,000 fine in respect of the sixth charge. He appealed against convictions and sentences before me. The prosecution cross-appealed against the sentences passed. 3 It was not disputed that access to the sensitive and vital controls required special access codes. Mr Wee, counsel for the appellant, submitted that this was not a case of computer hacking because the appellant was working on a project for his employers at the MBS and was authorised to access the system. Counsel submitted at length as to the chain of command from the MBS to the main contractor, to PA and argued that the appellant had not misunderstood or overstepped his authority. What was being overlooked however, was that the appellant went through an elaborate process to give himself remote access through his personal computer, and further, he added the email address

‘ernie.masih@gmail.com’ (which was his but not used since 2009 and was not an address known to his employers) to the system administrator in order to gain access to the system. The unanswerable evidence was that the appellant completed the layers of security commands in order to execute the instruction causing the blackout. The procedure required for such an instruction to be executed ruled out an accidental activation of the command. The inescapable conclusion that must be drawn from all these acts is that the appellant deliberately intended to cause the blackout. When there were no instructions or reasons for doing so, the natural inference must be that he did so with mischief in mind. It might be that the appellant was angry with MBS or his employer (we do not know), but his actions were clearly an offence under s 3 of the Act. He had no authority to access the computer, let alone use it to create a blackout at MBS. The trial judge noted the inconsistent statements of the appellant as to whether he committed the act under the sixth charge deliberately, and found the appellant’s explanation to be without merit. The appeal against conviction is accordingly dismissed. Although the appellant appealed against the sentences imposed, counsel did not address me as to why he thought the sentences were manifestly harsh. In my view (with the exception of the sentence in respect of the

sixth charge which I shall discuss shortly), they were not. I shall now address the Public Prosecutor’s appeal against the sentences, as well as the sixth charge in respect of the appeal by the appellant. 4 Mr Ong, the DPP submitted that the sentences were inadequate and that a substantial fine be imposed on the first five charges and a higher term of imprisonment in respect of the sixth charge. Instead of the term of two weeks’ imprisonment, the learned DPP submitted that the sentence should be enhanced to eight weeks. Mr Ong submitted that the act under the sixth charge amounted to ‘an intentional sabotage’. The sixth charge is basically an enhanced version of a charge under s 3(1), and because damage is caused, the sentencing court has the power to impose an enhanced sentence of up to $50,000 fine or to imprisonment of a term not exceeding seven years or to both fine and imprisonment. In contrast, a conviction under s 3(1) attracts the punishment of a fine not exceeding $10,000 or imprisonment not exceeding three years or to both fine and imprisonment. The key to the enhancement under s 3(2) lies in the phrase ‘If any damage is caused’. Damage is not any damage but damage as defined in s 2 of the Act. Section 2 defines damage as follows: ‘damage’ means, except for the purposes of section 13, any impairment to a computer or the integrity or availability of data, a program or

system, or information, that – (a)causes loss aggregating at least $10,000 in value, or such other amount as the Minister may, by notification in the Gazette, prescribe except that any loss incurred or accrued more than a year after the date of the offence in question shall not be taken into account; (b)modifies or impairs, or potentially modifies or impairs, the medical examination, diagnosis, or treatment or care of one or more persons; (c)causes or threatens physical injury or death to any person; or (d) threatens public health or public safety. 5 It will be seen that the four instances of damage are very specific. In the case of (d), there may also a distinction between ‘public health’ and ‘public safety’. It is the duty of the prosecution to ensure that all the particulars that constitute a charge are given so that the accused knows exactly what he needs to defend himself against. In the instance case, the original sixth charge appears to specify that the damage was under s 3(2)(a) because it contained the phrase ‘of at least $10,000’ immediately after the words ‘causing damage’ in the charge. However, the charge was then amended with the words ‘of at least $10,000’ struck out. That indicated that the prosecution was not going to allege and prove that the accused caused damage of at least $10,000. But what then was the damage caused? That the charge did not say, nor was

any evidence led detailing so. The defence did not point it out, and the trial judge assumed that damage was proved. He held that ‘Financial losses would also have been sustained through a stop in the operations of the casino business. Inevitably, the reputation of the MBS would also have been marred as it would have ruined the experience for their patrons.’ With respect, that was not the damage that the prosecution had particularised and a loss of reputation is not defined as damage under the Act. Before me the DPP submitted that the trial judge failed to take into account that the blackout was caused in ‘one of Singapore’s integrated resorts, whose development and opening were widely publicised worldwide and attracted overwhelming media attention and scrutiny.' The DPP went on to submit that the ‘MBS was also the pinnacle of Singapore’s tourism industry at the time, and both its recent launch and its unique contribution to the Singapore skyline drew international attention.’ These are clearly not matters that are within the definition of ‘damage’ in s 2 of the Act. Private practice lawyers and the civil court might be interested in the reputation and standing of a private institution, but those are not matters that are the concern of the public prosecution service and the criminal court generally, and in this offence specifically. 6 It was only on appeal that the DPP

submitted that a blackout might be a threat to public safety. That might be a common sense proposition but it was not particularized in the charge and was thus not the prosecution’s case at trial. Neither was evidence led to support it. Since damage was not particularised or proved and since the trial judge did not make any findings on such damage based on any evidence (since such evidence was not presented before the court), the sixth charge was only a charge under s 3(1), and though properly convicted as such, the sentence ought be neither more or less than the sentences of the five other similar charges. I will amend the sixth charge by deleting the words ‘Section 3(2) read with’, and vary the sentence to a fine of $3,000, and in default, three weeks imprisonment. Conduct constituting an offence under s 3 of the Act can vary widely in scope and nature. An offence under s 3(2) will very likely attract custodial sentence, and an offence under s 3(1) may similarly attract a custodial sentence if sufficiently grave and serious even though no damage was caused. Copyright © Government of Singapore. This judgment text has undergone conversion so that it is mobile and web-friendly. This may have created formatting or alignment issues. Please refer to the PDF copy for a print-friendly version. Version No 0: 25 Jul 2013 (00:00 hrs) ©

SUPREME COURT

SUBSCRIBE TO SUPREME COURT

REPORT VULNERABILITY

TERMS OF USE

PRIVACY STATEMENT

SUPPORTED BROWSERS Last updated: 28 Apr 2026

Source wording is retained. Consult the source document for its original formatting and pagination.

Authorities

Authorities used by the court

Cases, legislation, regulations, and constitutional provisions identified in the available record.

Computer Misuse Act (Cap 50A) s2

Legislation

Legislation referenced in the available case record.

Computer Misuse Act (Cap 50A) s3(1)

Legislation

Legislation referenced in the available case record.

Computer Misuse Act (Cap 50A) s3(2)

Legislation

Legislation referenced in the available case record.

Case-aware research

Ask AI about this case

The judgment and available research above are public. New questions open in a separate private conversation grounded in this case.

About this LexChat collection

This page organizes the available case record for research. Verify quotations, current status, and subsequent treatment against the source document. Corrections can be reported to hello@esheria.ai.

Legal information, not legal advice. Research summaries do not replace the judgment.