Hello,
I've pushed some updates to the malware store. Please look at the malware and/or download the malware. I pushed more after Christmas, but I forgot I did, but whatever.
pic: unrelated
https://vx-underground.org/Updates
I've pushed some updates to the malware store. Please look at the malware and/or download the malware. I pushed more after Christmas, but I forgot I did, but whatever.
pic: unrelated
https://vx-underground.org/Updates
π₯°41π«‘12β€7π3π’1
This media is not supported in your browser
VIEW IN TELEGRAM
I can't post this on Twitter because the nerds on Twitter wouldn't get it. Telegram gets it though.
π₯150β€26π13π₯°9π€£6π4π’1π―1π€1
The internet is cool and badass. You can just do things.
I found a man on YouTube who has repeatedly recorded himself knocking himself unconscious by performing WWE-like stunts onto things such as microwaves.
I'm not entirely sure of his motivations, but this person is so unusual I went WAY out of my way to acquire their autograph.
I subsequently framed it and placed it on my wall.
I found a man on YouTube who has repeatedly recorded himself knocking himself unconscious by performing WWE-like stunts onto things such as microwaves.
I'm not entirely sure of his motivations, but this person is so unusual I went WAY out of my way to acquire their autograph.
I subsequently framed it and placed it on my wall.
π€£80β€19π’8π₯2π₯°2π«‘2
vx-underground
The internet is cool and badass. You can just do things. I found a man on YouTube who has repeatedly recorded himself knocking himself unconscious by performing WWE-like stunts onto things such as microwaves. I'm not entirely sure of his motivations, butβ¦
Link for education: https://www.youtube.com/shorts/plM7CMmlwlg
YouTube
Flying elbow drop onto microwave ( WWE CM PUNK STYLE )
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
π€£47π₯°7β€5π€5π«‘3π₯1
In 2025 there was approx. 996 malware defense and/or detection research papers released.
π€59π₯°11β€8π3π’1
vx-underground
In 2025 there was approx. 996 malware defense and/or detection research papers released.
AND YALL MFERS ASKING "OHHH HOW DO I GET INTO MALWARE REVERSE ENGINEERING" READ LITERALLY ZERO
wAK=E UP BRO, LOCK IN
wAK=E UP BRO, LOCK IN
π₯°64π―35π€13π€£7π€3β€2π«‘2π₯1π’1π€©1
Earlier today I made a post about over 900 malware research papers being released in 2025. Some people expressed confusion about this. Let's talk about malware research, what it entails, blah blah blah.
Malware research can be broken down into two distinct categories and from there it can be broken down further into more unique categories. Let's keep it shrimple.
- Offensive malware research
- Defensive malware research
Offensive malware research is trying to find new malware techniques. This is pretty broad. I won't go too much into detail on this. This isn't the thingie we're discussing here.
Defensive malware research is documenting new malware campaigns, tracking existing malware campaigns, reverse engineering malware and correlating it and/or tying it to other malware campaigns, techniques on malware detection, etc. This can be pretty broad too because malware detection, malware campaigns, anti-malware research, etc. will be vastly different on Windows, Linux, MacOS, mobile-devices, etc.
When I write that there was 996 malware research papers released what it means is (approx.) "996 vendors released papers sharing information on malware campaigns, reverse engineering malware, sharing malware detection techniques, malware family lineage discoveries (shared code across malware campaigns), etc".
Every single day I see vendors release paper documenting malware campaigns, what they're seeing on their side, and methods to detect the malware payloads. How they're discovered is also a different discussion for a different day.
Places where malware research is released:
- Basically every government on the planet
- Hundreds of independent researchers
- Google
- SentinelOne
- ESET
- Microsoft
- Kaspersky
- CrowdStrike
- RecordedFuture
- Cisco Talos
- VMWare
- CloudFlare
- Akamai
- HuntressLabs
- BitDefender (also Huntress?)
- Fortinet
- AVAST / AVG
- TrendMicro
- Sophos
- F-secure
- Panda
- Comodo
- Qihoo
- Dr. Web
- NVIDIA
- Norton
- MalwareBytes
- Secureworks
- ZScaler
- Okta
- Chainalysis
- Trustwave
- Nextron Systems
- GDATA
- AT&T
- Walmart
- StealthMole
- Censys
- AhnLab
- PtSecurity
- OxSecurity
- Securonix
- Koi-AI
- Palo Alto Networks
- CheckPoint
- Huorong
- Oligo
- Cyderes
- DarkTrace
- K7Computing
- CyberArmor
- ... more ....
Malware research can be broken down into two distinct categories and from there it can be broken down further into more unique categories. Let's keep it shrimple.
- Offensive malware research
- Defensive malware research
Offensive malware research is trying to find new malware techniques. This is pretty broad. I won't go too much into detail on this. This isn't the thingie we're discussing here.
Defensive malware research is documenting new malware campaigns, tracking existing malware campaigns, reverse engineering malware and correlating it and/or tying it to other malware campaigns, techniques on malware detection, etc. This can be pretty broad too because malware detection, malware campaigns, anti-malware research, etc. will be vastly different on Windows, Linux, MacOS, mobile-devices, etc.
When I write that there was 996 malware research papers released what it means is (approx.) "996 vendors released papers sharing information on malware campaigns, reverse engineering malware, sharing malware detection techniques, malware family lineage discoveries (shared code across malware campaigns), etc".
Every single day I see vendors release paper documenting malware campaigns, what they're seeing on their side, and methods to detect the malware payloads. How they're discovered is also a different discussion for a different day.
Places where malware research is released:
- Basically every government on the planet
- Hundreds of independent researchers
- SentinelOne
- ESET
- Microsoft
- Kaspersky
- CrowdStrike
- RecordedFuture
- Cisco Talos
- VMWare
- CloudFlare
- Akamai
- HuntressLabs
- BitDefender (also Huntress?)
- Fortinet
- AVAST / AVG
- TrendMicro
- Sophos
- F-secure
- Panda
- Comodo
- Qihoo
- Dr. Web
- NVIDIA
- Norton
- MalwareBytes
- Secureworks
- ZScaler
- Okta
- Chainalysis
- Trustwave
- Nextron Systems
- GDATA
- AT&T
- Walmart
- StealthMole
- Censys
- AhnLab
- PtSecurity
- OxSecurity
- Securonix
- Koi-AI
- Palo Alto Networks
- CheckPoint
- Huorong
- Oligo
- Cyderes
- DarkTrace
- K7Computing
- CyberArmor
- ... more ....
π₯°47π21β€9π’1
vx-underground
Earlier today I made a post about over 900 malware research papers being released in 2025. Some people expressed confusion about this. Let's talk about malware research, what it entails, blah blah blah. Malware research can be broken down into two distinctβ¦
It should be noted that each vendor, or government, releases research which is tailored to them or their audience.
As you could probably assume, Microsoft rarely discusses MacOS malware.
Another interesting quirk is each vendor tailors research to their region. Vendors in China or Russia will discuss threats to the country they reside in. Hence, you can get unique insight into what is targeting countries outside the United States or NATO.
Believe it or not, while the United States says Russia and China launch offensive cybersecurity operations, China and Russia also accuse the United States (and allies) of targeting them as well! Strange stuff!
As you could probably assume, Microsoft rarely discusses MacOS malware.
Another interesting quirk is each vendor tailors research to their region. Vendors in China or Russia will discuss threats to the country they reside in. Hence, you can get unique insight into what is targeting countries outside the United States or NATO.
Believe it or not, while the United States says Russia and China launch offensive cybersecurity operations, China and Russia also accuse the United States (and allies) of targeting them as well! Strange stuff!
π₯°46β€14π±7π’1
No, Ubisoft was not compromised from their "anti-cheat".
No, Ubisoft was not compromised by a rogue agent.
No, Ubisoft was not compromised as a result of a Threat Actor infecting an employee with information stealer malware.
Ubisoft technically* wasn't "compromised" (hacked) in the traditional usage of the word. I can't go into too much detail, because I don't want my knee caps broken with a baseball bat, but the event we all witnessed was the result of API abuse
In simpler terms, nerds discovered an exposed API endpoint (computer where instructions are sent to) and abused the poop out of it. This endpoint received commands for all sorts of stuff (bans, credits, etc). Normally another program sends instructions to this endpoint.
Under normal conditions, this endpoint requires authentication with a "key" (instead of using a username and password), but nerds ... sort of ... found a way to bypass the API key requirement. I'm using the word bypass here extremely liberally. What happened was extremely silly.
Ubisoft is aware of what happened. They're not dumb. The fix for the issue they're encountering is kind of a pain in the ass to fix, it'll take some time, I'm not surprised nerds managed to metaphorically kick in the door (abuse the API endpoint) again.
Ubisoft itself was not compromised. No employee data was stolen. No customer data was stolen. Nerds basically beat Siege servers with a stick until it did stuff.
No, Ubisoft was not compromised by a rogue agent.
No, Ubisoft was not compromised as a result of a Threat Actor infecting an employee with information stealer malware.
Ubisoft technically* wasn't "compromised" (hacked) in the traditional usage of the word. I can't go into too much detail, because I don't want my knee caps broken with a baseball bat, but the event we all witnessed was the result of API abuse
In simpler terms, nerds discovered an exposed API endpoint (computer where instructions are sent to) and abused the poop out of it. This endpoint received commands for all sorts of stuff (bans, credits, etc). Normally another program sends instructions to this endpoint.
Under normal conditions, this endpoint requires authentication with a "key" (instead of using a username and password), but nerds ... sort of ... found a way to bypass the API key requirement. I'm using the word bypass here extremely liberally. What happened was extremely silly.
Ubisoft is aware of what happened. They're not dumb. The fix for the issue they're encountering is kind of a pain in the ass to fix, it'll take some time, I'm not surprised nerds managed to metaphorically kick in the door (abuse the API endpoint) again.
Ubisoft itself was not compromised. No employee data was stolen. No customer data was stolen. Nerds basically beat Siege servers with a stick until it did stuff.
β€βπ₯53π€£32β€13π―6π₯°2π€2π’1
The unfortunate reality is that I know dozens of people who have tried to notify vendors, or government agencies, of vulnerabilities or potential problems. For reasons I do not understand, sometimes things are brushed aside, or forgotten, or mishandled, and nothing is resolved.
Interestingly, and for reasons I do not understand, if they (the person who found the potential problem or vulnerability) notify me of the problem and I make a post on social media about it (to nearly 400,000 people), suddenly the issue is far more important and it is magically resolved.
I hate to say it, but sometimes you kind of have to bully and/or shame places into fixing things. I don't necessarily blame the security teams, I think it is a bureaucracy issue and/or management issue.
Interestingly, and for reasons I do not understand, if they (the person who found the potential problem or vulnerability) notify me of the problem and I make a post on social media about it (to nearly 400,000 people), suddenly the issue is far more important and it is magically resolved.
I hate to say it, but sometimes you kind of have to bully and/or shame places into fixing things. I don't necessarily blame the security teams, I think it is a bureaucracy issue and/or management issue.
π―71π€£15β€9π4π₯°2π’2π±1
This media is not supported in your browser
VIEW IN TELEGRAM
HOLY SHIT. Razer has demoed Razer Project AVA, a 3D Hologram AI companion.
Dawg, it's a fucking AI HOLOGRAM DESKTOP WAIFU
Dawg, it's a fucking AI HOLOGRAM DESKTOP WAIFU
π€£88π18π₯°7π±6β€βπ₯3β€2π€2π1π’1
vx-underground
HOLY SHIT. Razer has demoed Razer Project AVA, a 3D Hologram AI companion. Dawg, it's a fucking AI HOLOGRAM DESKTOP WAIFU
Dawg, the split second I saw I could have that niche Japanese internet celebrity lady living in a fucking jar on my desk, I immediately pre-ordered this fucking thing
π€£85π10β€7π’6π2π₯2π₯°2π2
Everyone sobbing and crying over the Razer Project AVA 3D Anime Waifu Hologram companion is being a big baby
The device Razer is selling requires a connection to a Windows device over USB. Hence, this device requires (in some capacity) drivers (kernel mode components). What I suspect (pure speculation) is when you purchase this device you'll need to install a Razer service (program running constantly) which will run as a service (Windows service, SYSTEM-level authority) somewhere on the machine. I suspect a user-mode component will be displayed which allows you to configure your 3D Waifu thingie.
I am profoundly curious what this looks like under the hood. "Hologram" technology aside, I want to look at the user mode components, the kernel mode components, the network requests it makes. I want to know what it's written in. Python compiled to .exe? Is it an Electron app (common now)? C/C++? Trendy and hip in Rust?
I am also deeply curious on the pricing model they push.
This (in my opinion) is a really interesting piece of technology. I really, really, really want to poke it with a stick to see how it works internally. What happened to nerds being curious and excited about stuff? Jesus
The device Razer is selling requires a connection to a Windows device over USB. Hence, this device requires (in some capacity) drivers (kernel mode components). What I suspect (pure speculation) is when you purchase this device you'll need to install a Razer service (program running constantly) which will run as a service (Windows service, SYSTEM-level authority) somewhere on the machine. I suspect a user-mode component will be displayed which allows you to configure your 3D Waifu thingie.
I am profoundly curious what this looks like under the hood. "Hologram" technology aside, I want to look at the user mode components, the kernel mode components, the network requests it makes. I want to know what it's written in. Python compiled to .exe? Is it an Electron app (common now)? C/C++? Trendy and hip in Rust?
I am also deeply curious on the pricing model they push.
This (in my opinion) is a really interesting piece of technology. I really, really, really want to poke it with a stick to see how it works internally. What happened to nerds being curious and excited about stuff? Jesus
β€62π₯°14π―9π«‘7π4π’1
vx-underground
Everyone sobbing and crying over the Razer Project AVA 3D Anime Waifu Hologram companion is being a big baby The device Razer is selling requires a connection to a Windows device over USB. Hence, this device requires (in some capacity) drivers (kernel modeβ¦
When everyone was crying about Copilot on Windows, I didn't see anyone (to my knowledge, I dunno) actually try to poke it with a stick to see what it was doing under the hood. I poked it and people read about it (and got some super cool feedback too). What happened to your curiosity? Why is everyone so fucking grumpy now? It's interesting stuff, dawg.
π€£52β€15π8π6π’5π₯°2
New research thingie.
Stupid callbacks
https://malwaresourcecode.com/home/my-projects/proof-of-concepts/stupid-callbacks-for-malware-evasion
Stupid callbacks
https://malwaresourcecode.com/home/my-projects/proof-of-concepts/stupid-callbacks-for-malware-evasion
Malwaresourcecode
Stupid callbacks for malware evasion | malware source code
π₯°30β€13π’1
Archived post, thing, on reverse engineering Microsoft Copilot
https://malwaresourcecode.com/home/my-projects/write-ups/some-quick-notes-on-microsoft-copilot
https://malwaresourcecode.com/home/my-projects/write-ups/some-quick-notes-on-microsoft-copilot
Malwaresourcecode
Some quick notes on Microsoft Copilot | malware source code
β€23π₯°4π’1