Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not run ActiveX dll after BitMono crypted. #171

Open
Zeki-Gursoy opened this issue May 9, 2024 · 10 comments
Open

Can not run ActiveX dll after BitMono crypted. #171

Zeki-Gursoy opened this issue May 9, 2024 · 10 comments

Comments

@Zeki-Gursoy
Copy link

Zeki-Gursoy commented May 9, 2024

I wrote Net FW 4.8.1 dll and create TLB. Dll can not load in Excel VBA. I get "Automation error". Trying 32 and 64 bits.

@sunnamed434
Copy link
Owner

Hi, can you send the Protections.json file, and the logs you got from BitMono

@Zeki-Gursoy
Copy link
Author

Of course... I attached.
.
bitmono-2024-05-09-22-02-45.log

protections.json

@sunnamed434
Copy link
Owner

[2024-05-09 22:02:47 WRN][BitMono.Obfuscation.Notifiers.ProtectionsRuntimeMonikerNotifier] [!!!] UnmanagedString - Intended for .NET Core runtime
[2024-05-09 22:02:47 WRN][BitMono.Obfuscation.Notifiers.ProtectionsRuntimeMonikerNotifier] [!!!] UnmanagedString - Intended for .NET Framework runtime
[2024-05-09 22:02:47 WRN][BitMono.Obfuscation.Notifiers.ProtectionsRuntimeMonikerNotifier] [!!!] AntiDecompiler - Intended for Mono runtime
[2024-05-09 22:02:47 WRN][BitMono.Obfuscation.Notifiers.ProtectionsRuntimeMonikerNotifier] [!!!] BitDotNet - Intended for Mono runtime
[2024-05-09 22:02:47 WRN][BitMono.Obfuscation.Notifiers.ProtectionsRuntimeMonikerNotifier] [!!!] BitMono - Intended for Mono runtime

First of, when you see Intended for <...> runtime its means specific feature is only able to work on the provided runtime. By this I mean probably this is why your .dll can't be used normally, I'd recommend to disable next features: AntiDecompiler, BitDotNet, and BitMono.

But, to ensure it work fine, keep only AntiILdasm feature as single enabled feature in protections.json and try to repeat the same thing you did before and let me know if it work or not

@Zeki-Gursoy
Copy link
Author

Zeki-Gursoy commented May 11, 2024

I tried all protection options one by one.
My dll code not work in VBA below options:
Also, BitMono app converts AnyCpu dll to 32 bit dll.

  1. NoNamespaces
  2. FullRenamer
  3. DotNetHook
  4. BitMethodDotnet
  5. BitDotNet
  6. BitMono

@sunnamed434
Copy link
Owner

sunnamed434 commented May 12, 2024

Ok. Try to do this

@Zeki-Gursoy
Copy link
Author

Zeki-Gursoy commented May 12, 2024

I tried...

  • BitMono App still Dll converting to 32 bit.
  • I set (top) "2.FullRenamer" true and retry with BitMono. "Automation Error" message still go on in VBA. If without this option works but, dll readable with ILSPY.

Have you idea?

@sunnamed434
Copy link
Owner

  1. Ok, I'll try to make a fix
  2. Can you enable only AntiIldasm feature, and let me know if it work

@Zeki-Gursoy
Copy link
Author

Ok, I tried only "AntiIlDasm" VBA code works. But, DLL code full readable with ILSPY.

@sunnamed434
Copy link
Owner

Nice that it work. I guess FullRenamer was breaking smth in your code

@sunnamed434
Copy link
Owner

Try to use CallToCalli, it should work fine and hide some code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants