Security Through Virtualization Obscurity

科技中介服务机构如何利用数智工具提升服务效率?.docx 科技中介服务机构如何利用数智工具提升服务效率? 立即下载
By: HolaHola Security Through Virtualization Obscurity

Prologue

Presented in the beginning of the 2008 Hypersight Rootkit Detector was immediately rumored and gained a lot of myths just like Rustock.C. Their homepage ,http://northsecuritylabs.com, here you can also download the latest version of this program. Authors of this program claimed it as
"World’s first Fourth-Generation rootkit detector". It is a bullshit. And we will tell you why.


1. The First VIPS
2. Actual View of Things or the Mysterious Ring -1
3. Security Through Virtualization Obscurity
4. Epilogue


1. The First VIPS


Mostly rumored at the beginning this unknown North Security Lab was immediately linked with our UG North as a continuing of the RKU project.
The most most surprising here the obstinacy of some persons which begun collecting rumors and creating new ones, about the detector and about it's authors. We would like to officially tell everybody that we have nothing with this unknown "North Security blah blah blah". More to say, we thinking this is a another scope of former carders who are trying to begin new life with an another white project related to security. The examples of such behaviour can be found not only in Russia.

This detector uses Intel VT technology built in the new Intel chips generation Core2 and AMD-V analogue. This is kind of Blue Pill in the security sphere, and as it was with Blue Pill here more rumors and myths than real usefulness. As you understand this program will not work on the old machines without Virtualization support, that is the huge percent of all available computers. They even created the new brand name for its project - Virtual Intrusion Prevention System aka VIPS. This is kinda bullshit and as were shown by Rustock.C this old rootkit were isn't supervised by VIPS just because it gained control on the system much more earlier and HRD were unable to decide.

2. Actual View of Things or the Mysterious Ring -1

What is the Ring 0xFFFFFFFF aka Ring -1?

It is kind of Hypervisor. You can find some part of it even now in Windows Server 2008. You can find a lot of useful information in the Mark Russinovich article about Ring -1, check his blog at Microsoft TechNet, you can also gain more information about virtualization from the VMWare Inc. publications.

Hypervisor gives ability to control the following components: i/o ports requests, memory, CPU registers. Something else? No, that is all folks. Is it enough for rootkit detection? Presumable yes? Ye.. Of course no. Why?

To do successful detection of real kernel mode backdoors aka rootkits it is not enough to simple supervise register changes or attempts to read/write at some addresses. To gain a REAL supervision over the system the antirootkit (lets call it VIPS if they so wish) should firstly control the file systems, the operation system specific data and structures. Here we are seeing the first but the dead for this concept reefs. Emulation of the file systems will reduce performance of any computer and will results in the numerous system/software configuration related bugs with third-party hardware or for example, lets take a RAID. Don't forget about OS-dependent issues, for example with W2k08. And that is all, VIPS going to the trashcan, because what do you want - a workable computer or the totally fucked and screwed virtual machine that will hung, fly in blue screens country only when you decide to change something in the hardware etc. Another fuck for the VIPS is the its communication with operation system. No matter hows good this Virtual Machine (we believe it is very poorly coded even now, because we have successfully started this crap only after numerous attempts on the different configurations of Intel Core2 Duo/Quad) it is required the same system data and structures. And don't you think that it is very hard to fake them specially for the this virtual machine? Nope. And what about user mode stuff? It isn't changing registers and doesn't attempts to write data somewhere in kernel mode, but it is not less rootkits than they kernel mode brothers And what about the other categories of rootkits, such as keyloggers for example? What about rootkits which will loads before VIPS? What about legitimate software? FSD filters? Encryption software? CD/DVD emulation software? DRM? They all will be flagged by VIPS? So it is completely unknown for what exactly this program was created because it is simple useless at this point. The same existing antirootkits (so called 1-3 generations) can find much more than any VIPS can gather through it a priory buggy and slow virtualization. Lets remember for what exactly VT was introduced, was it introduced for security software? No. We feeling yourselfs just like tourists in the fucken zoo where big boys and girls playing with monkeys and operating the words and terms they do not understand. We wouldn't be wondered if after beta testing this "Four generation antirootkit" will became a paid program.

Call this nonsense 4 generation rootkit detector is just like call Kaspersky AV - the most technically advanced antivirus. The same edges just in profile, well, russian speaking readers will understand this point :D

Bypassing this idiocy doesn't requires something specific. You can modify the SSDT for example without resetting write protection bit, you can successfully hide processes, drivers, files or keys without any notice of this "detector". DKOM and DKOH still here. CmRegisterCallback still here. Trying to control all these stuff will force VIPS to output any sneezes from the system. But if the authors really wants to know, it is exists the strong methods which can help to identify VIPS and shut it fucken down. In the end user mode rootkit part can gain access to the VIPS components and simple turn them off. Of course it is needed to identify the VIPS, but at the current level of its implementation it is very to done. What about future here can be used specially organized timing attacks which will successful not only with VIPS but with Blue Pill also.

We are not telling about the hybridizing of the rootkit with operation system (this is started with Rustock.C and will be continued we for sure) and VIPS will be useless at this point. So the VIPS will require a long white list of trusted components and trusted areas, the same what we actually seen currently with HIPS. Where is the Know How here? Finally this program unfamilar with "anti" part.

This is still unknown what this program will do on the systems with disabled virtualization support. As it shows on our machines it is simple dies. Such kind of security programs have no future. The further operation system versions can and it is most likely will use the own hypervisor implementation and will not let such programs normally working. So for what purpose this all was started?

So this whole story with "World’s first Fourth-Generation rootkit detector" remembers us another Fairy Tales from Russia.

In another hand lets see hows Microsoft realized Hyper-V in Windows 2008. Hyper-V is the virtualization platform INTEGRATED with the operating system and considered as three main components: the hypervisor itself, virtualization stack and the virtualized IO model. The hypervisor basically acts to create the different "partitions" that each virtualized instance of code will run. The virtualization stack and the IO components provide interactivity with Windows itself and with the various partitions that are created. All three components work in "tandem". Using servers with processors equipped with Intel VT or AMD-V technology (which of course must be enabled), Hyper-V interacts with the hypervisor, which is a very small layer of software that is present directly on the processor. This software hooks into threads on the processor that the host operating system can use to efficiently manage multiple virtual machines and multiple virtual operating systems, running on a single physical processor. Do you feeling the difference between dilettantes from North Security and Microsoft? Of course Hyper-V isn't security components, but it is much more close to it than any of VIPS will be.

3. Security Through Virtualization Obscurity

It is unknown why almost all smart guys and girls in this world have completely "put on detection" (ignored it) and started inventing a bicycle. Maybe because they are not so smart guys and girls as they think?
Every new term and technology starts a ridiculous circus around it. There is the good example - Data Execution Prevention technology built in Windows XP SP2. And what, does it really helps? Mostly incompetent people starting circus around every new term and new technology, even if it is so cool as VT is. Do not look for a black cat in the darkness.

What HIDS gives to you?
Checking by in advance programmed criteria of certain places and objects of the operation system and its environment.

What is the weakness points of this?
Compromised criteria and methods, "Vision horizon" problems of antirootkits especially.

What HIPS gives to you?
Control over the system via documented and not documented features and places.

What is the weakness points of this?
Does it controlling enough? No. It is acting like intrusion software and not a part of OS. Dead-end by design, when this software can't decide automatically it gives user to choose what he/she will do next. Rules problem. Dead-end by design when the malicious software compromises security system in the methods.

What VIPS gives to you?
Controlling? No mostly observing of the several system areas.

What is the weakness points of this?
There is no future for only VT based detection. Compromising at many points including methods, criteria and "vision horizon". Blind fate not in VT, blind fate in developers abilities to control, predict and prevent everything.

So all this weak. Not good enough, not modern HIPS, not modern antirootkits aka HIDS not VIPS.

But it is still possible to develop a close to perfect rootkit detection and removal software, but it will be ALWAYS operation system dependent and will COMBINE the numerous technologies maybe JUST maybe including this hardware VT, but not ONLY the one harmonious name, otherwise it simply idiocy and empty advertising of nothing.

The best way to detection software will be integration of it into the operation system core, which will make it much more powerful ever seen before. And only after this you can call it - The four, five, sixth generation rootkit detection and this will not sounds like a bullshit. The best approach to the system will be - to not let any unwanted software gain control over the system. All third-party protection are vulnerable to the attacks. HIPS always will be vulnerable because of the design Trust-Not-Trust dilemma. But even now without integration exists very good and free tools capable to detect most of the known and available shit and all them will work without any VT related idiocy. Lets leave VT for Virtual Machines support and start thinking by head not ass.

HIPS as well as this VIPS gives people wrong feeling of security without giving them this security. They both compromise your computer security just by their presence at your computer. Just look on the numerous bugs inside them. Instead of HIDS this systems working 24/7/365 (always since the os startups) and slowing down your computer. Wondering, why they using the undocumented features and hooks everything what can be hooked? The same design dilemma, but here it is inside dev's brains. You do not need all this hooking trash and you do not need this special "Hypervisor for good". You must be an user of computer not a slave of the security though obscurity.

And yeah rootkits here just because OS is not enough.

Epilogue.

That's how all this stuff actually looking:

Russian Former Carder (RFC) selling 0day detection software to the Naive European Casual (NEC), retrospective from bhc magazine:

RFC: Yo, bro. I have got some new eleven generation rootkit detector for sale! Wanna to buy? VT, BT, ZT technologies included!
NEC: 0_0 Sure! How much it will be?
RFC: Two hundred rubles.
NEC: Man, i don't give a fuck where you take these rubles.
RFC: 2k bucks and we have a deal then.
NEC: Yo! Done! I love Russia.

HolaHola aka DNY / VX Heavens
EP_X0FF / VX Heavens
MP_ART / VX Heavens

支付对账系统|Spring Cloud Alibaba微服务架构 分库分表+双边账比对引擎 一套基于 Spring Cloud Alibaba 的微服务支付对账系统完整工程,解决支付业务中"本地账与渠道账不一致"这一核心问题。技术栈为 JDK 8 + Spring Boot 2.7 + Spring Cloud 2021 + Nacos + OpenFeign + MyBatis-Plus + ShardingSphere 5.3 + Redisson + RocketMQ,共 8 个 Maven 模块、104 个 Java 文件、约 8800 行代码,含建表脚本与中间件编排文件。 工程按商户中心、渠道中心、结算中心、对账中心、调度中心、网关分层。核心实现有四块:一是双边账比对引擎,支持渠道单号优先、商户订单号回退的匹配主键,分位容差抹平,自动判定本地多单、渠道多单、金额不一致、状态不一致四类差异;二是差异处置策略,覆盖查单补偿、本地账补记、人工工单与挂账结转下期,并内置防资损约束——渠道查单接口失败时不判定为"渠道无此单",避免把超时误判成掉单而错误关闭已收款订单;三是分库分表落地,4 库 × 32 表,自定义按账期落表的分片算法,跨账期范围查询可精确裁剪表;四是渠道账单适配器,处理 GBK 编码、表头按列名定位、CSV 引号切分与金额元转分。网关侧实现了商户 HMAC-SHA256 签名验签加时间戳防重放、运营台 JWT 加登出黑名单双身份鉴权。另有雪花 ID、账期 T+N 计算、幂等切面、统一错误码与异常体系、对账任务状态机配分布式锁与乐观锁双保险。 立即下载

相关推荐

科技中介服务机构如何实现服务流程的标准化与高效化?.docx

科技中介服务机构如何实现服务流程的标准化与高效化?

Security+ 8. 实施密码技术

8. 实施密码技术8.1 密码学概念8.1.1 密码学元素8.1.2 散列概念8.1.3 数据状态8.1.4 密码套件(Cipher suite)8.2 加密算法8.2.1 密码的类型8.2.2 散列算法的类型8.2.3 对称加密算法的类型8.2.3 非对称加密算法的类型8.2.4 密钥延展算法的类型8.3 公钥基础架构(Public key infrastructure/PKI)8.3.1 PKI组件8.3.2 证书颁发机构[Certificate authority/CA]8.3.3 证书的类型8.3

f_carey的博客 823

JavaScript全栈工程化 Vite+React18+RTK中后台项目 性能优化实战

【内容概要】这是一个完整可运行的 JavaScript 全栈工程化实战项目,基于 Vite 5 + React 18 + Redux Toolkit 搭建,覆盖框架深度实战、工具链与工程化、性能优化三大方向。包含登录态管理、路由守卫、仪表盘、订单列表、用户管理、个人设置、性能监控 5 个业务页面;工程化方面配好了 ESLint + Prettier、Jest 单元测试、GitHub Actions CI、Sass 变量注入和路径别名;性能优化部分手写了 2000 条数据虚拟滚动、Vite manualChunks 分包、ECharts 动态加载与 dispose、Web Vitals(LCP/CLS/INP)埋点、useMemoryLeakDetector 内存泄漏检测 hook、防抖与 localStorage 持久化等常见优化手段,每项都在代码注释里讲了原理和踩坑记录。 【使用场景及目标】解压后 npm install && npm run dev 即可启动,自带 mock 数据不用起后端,登录账号 admin / 123456。可作为毕业设计、课程设计、面试演示项目,或在此基础上二次开发自己的中后台系统。跑 npm run build:analyze 可查看打包产物分析报告。

XCTF攻防世界Misc

ext3 下载附件是一个名为Linux的文件,无法打开,拖到虚拟机里,终端执行命令。 首先用strings命令来定位含有flag的文件:strings linux | grep flag 接下来用到的是mount命令,用来挂载Linux系统外的文件:sudo mount liunx /mnt 这句命令的意思就是,把Linux挂在 /mnt下面。这里是使用mount命令的意义。 最后直接查看/mnt...

paintShadow的博客 901

基于非对称纳什谈判的多微网电能共享运行优化策略(Matlab代码实现)

基于非对称纳什谈判的多微网电能共享运行优化策略(Matlab代码实现)内容概要:本文档标题为《Plecs全桥LLC谐振变换器仿真模型.txt》,但实际上内容并未围绕Plecs或全桥LLC谐振变换器展开详细论述,而是罗列了大量基于Matlab/Simulink和Python的科研仿真项目标题及相关技术方向,涵盖电力系统、无人机控制、微电网优化、路径规划、状态估计、信号处理、电动汽车调度、电力电子变换器等多个领域。其中包括多种优化算法(如粒子群、遗传算法、NSGA-II)、控制策略(如PID、MPC、滑模控制)、仿真建模(如LLC谐振变换器、DAB变换器、PWM整流器)以及具体应用场景的研究实现。尽管提及“隔离型全桥LLC谐振变换器建模及参数设计资料”,但全文缺乏对该主题的具体描述、模型细节或仿真分析,仅作为条目之一出现。因此,该文档实质是一份科研项目资源清单或代码合集目录,而非针对某一主题的深入文章。; 适合人群:具备一定Matlab/Simulink或Python编程基础,从事电气工程、自动化、控制科学、电力电子、新能源系统等相关领域的研究生、科研人员及工程技术人员。; 使用场景及目标:①为科研工作者提供丰富的课题参考与复现资源,涵盖优化调度、控制系统设计、电力电子仿真等方向;②辅助完成硕士/博士论文、期刊论文复现、课程设计或项目开发,提升研究效率与创新性;③通过已有模型和代码快速搭建仿真平台,聚焦算法改进与性能优化。; 阅读建议:此文档应作为科研资源索引使用,读者可根据自身研究方向筛选相关条目,结合配套代码与参考资料进行深入学习与实践。对于希望研究全桥LLC谐振变换器的用户,需注意本文档未提供完整内容,建议查找标注的“仿真+设计报告+计算书”等附件资源以获取详细信息。

高校技术转移办公室在推动成果转化过程中,如何高效完成技术成果的信息整合与价值挖掘.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

高校技术转移办公室人员在成果推介过程中,如何提升推介材料的专业性与吸引力.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

高校技术转移办公室人员,如何精准挖掘并分析企业的技术需求?.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

三电平Buck直流变换器双闭环、单闭环、开环仿真【附参考文献】(Simulink仿真实现)

内容概要:本文系统介绍了三电平Buck直流变换器在Simulink环境下的开环、单闭环及双闭环控制系统的建模仿真与性能对比分析,深入探讨了不同控制策略对系统动态响应、稳态精度、抗扰能力及鲁棒性的影响。通过构建完整的仿真模型,详细阐述了各控制结构的设计思路、关键模块实现方法及PI控制器参数整定过程,并结合仿真波形对比分析了三种控制方式在启动过程、负载突变等工况下的输出电压表现,充分验证了双闭环控制在抑制电压波动、提升调节速度和负载适应性方面的显著优势。文档还提供了详尽的参数设置指南和参考文献,便于读者复现结果并开展进一步研究。; 适合人群:电气工程、自动化、电力电子与电力传动等相关专业的本科生、研究生,以及从事直流变换器设计、控制算法开发和系统仿真的科研人员与工程技术开发者。; 使用场景及目标:①掌握三电平Buck变换器的工作原理与数学建模方法;②理解电压模式控制与电流模式控制的差异与应用场景;③学习双闭环PI控制器的设计流程与参数整定技巧;④为电力电子装置的控制器设计、性能优化及科研项目提供仿真验证平台与技术参考。; 阅读建议:建议读者结合Simulink软件动手搭建仿真模型,分步实现开环、单闭环与双闭环控制系统,通过调整控制器参数并观察不同工况下的系统响应,深入理解控制策略对系统性能的影响机制,同时结合提供的参考文献强化理论基础,实现从仿真到实际应用的有效过渡。

隔离型全桥LLC谐振变化器建模及参数设计资料【仿真+设计报告+计算书】

内容概要:本文档是一套关于隔离型全桥LLC谐振变换器的综合性技术资料,系统涵盖了拓扑建模、参数设计、闭环控制策略及仿真验证等关键环节。资料整合了Simulink仿真模型、详细设计报告、Mathcad计算书以及控制算法说明文档,深入探讨了恒压恒流双闭环控制、变频与移相混合控制、软启动机制等核心技术,并提供了多应用场景实例,包括双向全桥LLC、多相交错LLC以及电动汽车V2G系统中的CLLC变换器设计。此外,配套资源还包含了多种先进控制与状态估计算法(如EKF、UKF、PF及其与神经网络融合算法)的Matlab实现代码,强化了科研复现与工程实践能力。; 适合人群:适用于电气工程、电力电子及相关专业的研究生、科研人员,以及从事高频开关电源、新能源变换器开发的工程师;需具备扎实的电路理论基础与一定的仿真软件操作经验。; 使用场景及目标:①支持全桥LLC变换器的高效参数设计与动态性能优化;②服务于高校或企业的科研项目,助力拓扑创新与控制系统开发;③作为毕业设计、学术论文或工业级产品原型开发的重要技术参考,提升系统效率、稳定性和响应速度。; 阅读建议:建议结合Simulink仿真模型与Mathcad计算书同步学习,重点关注谐振元件匹配、控制环路设计与系统稳定性分析,充分利用提供的Matlab/Simulink环境进行仿真调试与二次开发,深化理论认知与实际工程应用的融合。

三相交错并联Buck变换器+低纹波输出+双闭环控制仿真【附参考文献】(Simulink仿真实现)

内容概要:本文详细介绍了基于Simulink平台构建的三相交错并联Buck变换器仿真模型,重点实现了低输出纹波特性和双闭环控制策略。通过三相交错并联结构有效抑制输入与输出电流的纹波成分,显著提升电源系统的稳定性和电能质量;控制系统采用电压外环与电流内环相结合的双闭环架构,增强了系统的动态响应能力和抗干扰性能。资源包涵盖完整的Simulink仿真模型、技术说明文档及参考文献,具有较强的工程实践价值,适用于电力电子变换器的科研开发与教学实验。; 适合人群:电力电子、电气工程及其自动化等相关专业的高校本科生、研究生及科研人员,尤其适合从事直流变换器拓扑结构与先进控制策略研究的专业人士,具备电路理论基础和Simulink仿真操作经验者更佳。; 使用场景及目标:①用于高效低纹波DC-DC变换器的拓扑创新与控制算法研究;②支撑科研项目中对多相并联技术与双闭环控制系统的性能验证;③作为课程设计、毕业设计或实验教学的技术范例,帮助深入理解交错并联的工作机理与闭环系统的设计方法。; 阅读建议:建议结合所提供的参考文献系统学习控制策略的理论依据,并动手调整仿真参数以观察系统在不同工况下的动静态响应特性,进一步掌握模型搭建、控制器设计与性能优化的全流程,强化理论与工程实践的融合能力。

SOP 配电网故障重构方法研究【IEEE33节点】(Matlab代码实现)

内容概要:本文档是一份关于Plecs全桥LLC谐振变换器仿真模型的技术资料汇总,重点介绍了隔离型全桥LLC谐振变换器的建模、仿真与参数设计方法。文档包含完整的仿真模型、设计报告和计算书,并基于顶级EI期刊研究成果进行复现,系统阐述了谐振变换器的工作原理、关键参数设计、软开关实现、效率优化以及动态性能分析等内容。通过Simulink/Plecs平台实现仿真,支持对变频控制、移相控制及模式切换等先进控制策略的研究,适用于电力电子变换器的科研与教学实践。; 适合人群:具备电力电子与电力系统基础知识,从事新能源、电源设计、微电网等相关领域的研究生、科研人员及工程技术人员。; 使用场景及目标:①用于高校或研究机构开展LLC谐振变换器的教学实验与课题研究;②支撑科研论文复现与创新性拓扑结构的验证;③为企业研发高效率DC-DC变换器提供仿真基础和技术参考; 其他说明:文档配套资源丰富,包含仿真文件、设计报告与参考文献,建议结合MATLAB/Simulink或Plecs软件进行实操演练,重点关注谐振参数匹配、软开关边界分析与闭环控制策略的设计。

产业园区运营负责人如何依托平台系统提升科技资源的集聚与转化效率?.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

科技中介服务机构如何建立标准化、可复制的服务流程?.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

高校技术转移办公室如何提升技术成果的精准推介效率?.docx

科易网基于AI模型+行业大数据,在技术转移、成果转化、技术经纪、知识产权、产业创新、科技招商等垂直领域的多样化应用场景,推出科技创新领域的AI+工具与数智化解决方案,推动科技创新与产业创新智能化发展。

XCP_Basic 移植步骤

XCP_Basic 移植步骤

ggzzc的博客 2316
上一篇: Vista System Restore Rootkit
下一篇: 修改一个结束进程的程序
iiprogram
博客等级 码龄25年 1068粉丝 1515原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值