2Q/3Q Loss b/c of Ransomware

anonymous

Guest
A vehicle needs an oil change / 3,000 miles. The vehicle will keep running w/o proper maintenance until catastrophic failure.

The stockholders never took a look at maintenance schedule before buying into MRK.

Individuals with direct exposure to the company can share first-hand accounts of how much has slipped.

Short term goals and making the balance sheets nice is the only priority. Removing cash from the company to profit the few and screw everyone else.

3 weeks idle that spanned 2Q and 3Q is a catastrophic failure.

Wait until the FDA finally sees the other things that have been neglected.
 






A vehicle needs an oil change / 3,000 miles. The vehicle will keep running w/o proper maintenance until catastrophic failure.

The stockholders never took a look at maintenance schedule before buying into MRK.

[...]

3 weeks idle that spanned 2Q and 3Q is a catastrophic failure.

Wait until the FDA finally sees the other things that have been neglected.

Why pay for oil and labor when you can put a two cent sticker over the "Check Engine" light and drive it until the wheels come off then buy a new vehicle.

It's the Merck way
 


















Based on sales of $39.8Bn in 2016 you could estimate a loss of $2.2Bn in revenue for 3 weeks lost production. Extrapolate that out for the duration of the incident then add to that, increased costs (Merck labor and external service contracts to assess and rectify the damage where possible, replacement systems where not), decrease in sales post-incident, the cost of replacement IT hardware and written-off product and you could guess we will probably be in the high-end of the estimate above.
 












3 weeks without declaring a disaster.

Go Team Merck!!!!


They are lying and telling the street that this was a small event and nothing was lost. Fact is - research is still idle and there is no end in sight as most of the system were not backed up.

I heard one if the IT leaders was on vacation and they contacted him and told him not to bother coming back to work.
 






They are lying and telling the street that this was a small event and nothing was lost. Fact is - research is still idle and there is no end in sight as most of the system were not backed up.

I heard one if the IT leaders was on vacation and they contacted him and told him not to bother coming back to work.
Research has been idle for 10 years. Maybe they will find out production has not changed and fire your ass.
 






Merck is still grappling with just how much damage they’ve incurred as a collateral victim of the NotPetya attack one month ago. And as a direct consequence, they’re cutting their profit outlook and signaling delays with some product supply orders.

The pharma giant disclosed the news this morning in their earnings report, with CFO Rob Davis telling analysts the company is still “assessing the full impact.” But it has clearly had an impact on the numbers. “The guidance would have been higher without the cyberattack,” Davis added.

Supplies of Keytruda, Januvia and Zepatier will not be affected, according to the drugmaker.

Shares $MRK were flat in mid-morning trading.

The company isn’t producing any bulk product yet from any of its own facilities, but supplies continue flowing from contract manufacturing relationships. In a statement to Endpoints News, Merck admits research has been affected, but would not elaborate on dosing interruptions or trial schedule changes.

The cyber-attack led to a disruption of our worldwide operations, including research. However, we have been able to maintain our clinical trial execution plan and we continue to pursue previously outlined priorities.

On June 27, thousands of companies around the world were hit by NotPetya — an exploit based on stolen NSA technology. Microsoft first encountered the virus with “worm capabilities” in 12,500 computers in Ukraine, which then spread laterally to another 64 counties including the United States, infecting computers that were not patched with critical updates.

Merck claims the patches were installed. At the time they said, “government authorities working with us have confirmed that the malware responsible for the attack contained a unique combination of characteristics that enabled it to infect company systems despite installation of recent software patches.”