Sponsored Content
Full Discussion: Our system was hacked
Special Forums Cybersecurity Our system was hacked Post 303037142 by jgt on Wednesday 24th of July 2019 05:19:52 PM
Old 07-24-2019
Our system was hacked

Someone made a mistake, and left our router wide open, pointing all ports to a SCO 6.0.0 system.
Within 24 hours, the following happened.
The contents of all the files (except tar files) in three directories, one directory on each of three different file systems, were replaced with nulls. None of the inode data was changed, meaning that the output of 'ls -l' was the same before and after. In two of the directories the file permissions were 0664, and in the last, the permissions were 0644 and files owned by root.
I have not been able to find anything in any of the log files to indicate who or when this happened.
Since we had adequate backups there was no long term damage.
Any thoughts would be appreciated.
This User Gave Thanks to jgt For This Post:
 

3 More Discussions You Might Find Interesting

1. Linux

pc hacked

Hi, i think someone has hacked my server, the following rules used to come which i haven't put. Please help me i couldnt find out how this rules are apply, i think someone has put an script which generates enables the rules. But after restarting the iptables everything seems to be working... (0 Replies)
Discussion started by: naik_mit
0 Replies

2. Cybersecurity

How to know when you've been hacked

One of the most important ways to keep tou machine secure is to know when it has been broken into. The less time hackers have on your system, the less they can do to it, and the greater you chancens of kicking them off and repairing the damage. The more sophisticated the hacker, the less likely... (8 Replies)
Discussion started by: binhnx2000
8 Replies

3. Cybersecurity

Server hacked on known port

Hi, There is a recent case whereby it was reported that one of the production servers was hacked on port 1521. However, I am not sure how this was possible, as I checked that the OS firewall (iptables) is on : # /etc/init.d/iptables status Table: nat Chain PREROUTING (policy ACCEPT) num ... (7 Replies)
Discussion started by: anaigini45
7 Replies
CHKSTAT(8)					      Tool to check and set file permissions						CHKSTAT(8)

NAME
chkstat - Tool to check and set file permissions SYNOPSIS
chkstat [--set|-set] [--noheader] [[--examine file ]...] [[--files filelist ]...] [[--root directory ]...] permission-file ... DESCRIPTION
The program /usr/bin/chkstat is a tool to check and set file permissions. Multiple permissions files can be given on the commandline. If the permission files contain multiple entries for a single file, the last entry found will be used. General Options --set, -set This option enables setting the file permissions, the default is to check and warn only. --noheader Omit printing the output header lines. --examine file Check permissions for this file and not all files listed in the permissions files. --files filelist Check permissions for the files listed in filelist and not for all files listed in the permissions files. --root directory Prefix the files given in the permissions files by this directory. EXAMPLE
The command chkstat -set /etc/permissions will parse the file /etc/permissions and set the access mode and the user- and group memberships each file listed. The format for the input file is FILEPATH OWNER:GROUP MODE and wildcards are not supported for the filepath. Lines starting with '#' and empty lines are treated as comments. COPYRIGHT
1996-2003 SuSE Linux AG, Nuernberg, Germany. 2008 SUSE LINUX Products GmbH AUTHORS
Reinhold Sojer, Ruediger Oertel, Michael Schroeder Useful changes and additions by Tobias Burnus 3rd Berkeley Distribution 2008-04-17 CHKSTAT(8)
All times are GMT -4. The time now is 09:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy