mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#powershell

26 Beiträge23 Beteiligte1 Beitrag heute

BERT Ransomware Group Targets Asia and Europe on Multiple Platforms

A newly emerged ransomware group called BERT has been targeting organizations across Asia and Europe since April. The group employs simple code with effective execution, impacting sectors such as healthcare, technology, and event services. BERT's ransomware operates on both Windows and Linux platforms, using PowerShell-based loaders, privilege escalation, and concurrent file encryption. On Linux systems, it can support up to 50 threads for fast encryption and forcibly shut down ESXi virtual machines. The group's tactics include disabling security features, terminating specific processes, and using standard encryption algorithms. BERT's variants have evolved, streamlining their encryption process and expanding their targeting activities. The Linux variant shows similarities to the REvil ransomware, suggesting possible code reuse.

Pulse ID: 686bb6597ce02f8f4a33b453
Pulse Link: otx.alienvault.com/pulse/686bb
Pulse Author: AlienVault
Created: 2025-07-07 11:58:17

Be advised, this data is unverified and should be considered preliminary. Always do further verification.

LevelBlue Open Threat ExchangeLevelBlue - Open Threat ExchangeLearn about the latest cyber threats. Research, collaborate, and share threat intelligence in real time. Protect yourself and the community against today's emerging threats.
Antwortete im Thread

@Edent

It is a shame that neither

> Resolve-DnsName -Name where-is-the-iss.dedyn.io -Type LOC

nor

> nslookup -type=loc where-is-the-iss.dedyn.io

work.

Not even @rmbolger 's Resolve-Dns supports the LOC resource record type.

Although I suspect that might be the Windows tool that gains support the most quickly, just for the bragging rights of being able to show an ISS LOC record in Windows when no-one else can. (-:

I'm working on v2.0 of TerminalBlocks. Which of these three #PowerShell examples is your favorite?

github.com/Jaykul/TerminalBloc

You can try the pre-release:
powershellgallery.com/packages

But it needs the pre-release of my Pansies module:
powershellgallery.com/packages

There's also a pre-release #PowerLine #prompt #module that helps build prompts with it, but docs need some work:
powershellgallery.com/packages

Seit 25 Jahren arbeite ich mit Linux und ja – Windows ist nicht das OS, das ich freiwillig nutzen möchte. Aber dieses ewige OS-Bashing erinnert eher an einen Streit auf dem Pausenhof als an einen erwachsenen Diskurs. Wer Spaß an seinem System hat, soll es nutzen. Linux ist solide, manchmal sogar elegant – aber kein Heilsversprechen. Und das muss es auch nicht sein.

Die Welt dreht sich weiter – ob mit #Bash oder #PowerShell spielt längst nicht mehr die Hauptrolle.

Hi #nerds, if I run a #powershell script that takes a directory or a collection of directories as its arguments, the trailing slash in the directory name turns the following single quote into a double quote using evil Microsoft dark magic somehow.
If my script is:
```
param (
[string[]]$inDirs
)
foreach ($dir in $inDirs){
write-host $dir
}
```
and I do
```
pwsh myscript.ps1 'c:\\some\dir\'
```
The result is
```
c:\\some\dir"
```
How do I get it to unescape (or whatever it's doing) the last slash?
#AskFedi #CodingHelp #pwsh