I've had a number of people approach me about their coins getting attacked by having the blockchain replaced with a longer chain, the longer chain released by the attacker is without certain transactions. The coin may be attacked but the target is normally an exchange, coins are sent to the exchange, sold for Bitcoin and then withdrawn, at that points the longer chain is released, the coins disappear from the exchange and the attacker gets their coins back. Small coins with low hash power are easy targets for attackers. This has caused a few coin pairs to be frozen and people to be in a panic.
PoW coins are the typical target for this type of attack, PoS coins are harder to target due to PoS block generation but not impossible if PoS generation is still very low. There have been many proposals for solutions to protect coins from a blockchain replacement attacks but for small coins the one solution that works and is available now is to use live checkpointing. Checkpoints are defined in Bitcoin source code by defining a block hash and height, clients will only connect to a chain that has the corresponding blocks, it is to make sure that clients connect to the correct main chain. Altcoins inherit this checkpoint system.
Realtime checkpointing was devised by SunnyKing developer of PeerCoin to protect the chain before PoS was sufficient. It protects the history of the chain by use of a node that will broadcast checkpoints at a certain height set in the conf file. If your coin is being attacked, your coin pair is locked on the exchange and you face potential delisting you may want to consider implementing realtime checkpointing. For reference there is a commit for checkpointing below (Deepcoin linked below was commissioned and not a project that I ran personally), instructions on how to use it is in the checkpointsync.cpp file. If you decide to use this system add a Peercoin copyright notice on the About dialog and COPYING file.
https://github.com/Deepcoinbiz/Deepcoin/commit/43413fac89da1db064668e7e4dd5bd6c6036dfb4