Skip to main content

遭遇黑客软件

昨晚突然发现电脑变慢，ps一看有好多以www用户名的进程，我可没有这个用户啊，再看那些进程，一堆scan和一个httpd等，真是可疑。

然后去/proc/查看，那些文件的可执行文件都位于/tmp/.a，里面除了这个scanner和httpd外，还有bruteforce和一个弱密码字典，以及一些扫描的log。 哇，中招了！

于是赶紧杀进程，然后想删掉这些文件，却总是报Segmentation fault, 之后又试了几个命令，也是报这个错，我看了一下/bin， 啊，原来很多命令的文件都被修改了。 于是重启，发现启动过程中都是Segmentation fault, 一下子懵住了。 当时太困了，不知所措，只好关掉等今天解决。

实在是不想重装，于是试图恢复，首先用live cd启动，把/bin的那些文件拷过去一份，然后搜了下/sbin,/usr/bin等重要文件夹，没有被改动的样子（这里/bin,/sbin,/usr/bin都是硬盘上的而不是live cd上的）， 之后，用chroot和aptitude重装了一下coreutils,为了保险，把一些*utils都重装了一下。

然后重启，似乎是正常了，松了一口气。但是还是要观望一段时间，看有没有什么遗留的。

现在想一下，根据那个文件夹里的log和字典文件推断，那个scanner是破解ssh里高权限用户的密码，然后一看我这里的root密码，天啊，原来是个弱密码，我才想起来当时装MySQL时图省事弄的，结果现在忘了。。真是敲响了警钟。

另外上网搜了一下相关资料，除了看到一个人跟我有类似情况外，没有别的有用的信息，看来这个东西还是挺新的。

现在赶紧把ssh的root登录关掉。

总之是第一次有这种经历，万幸阿，那个程序没给我rm -rf /, 我作业还没写完呢。。
Labels:

Comments

Post a Comment

Popular posts from this blog

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »