Skip to content
NewA calmer, faster ZeroHour

41-module PowerShell toolkit ran on unnamed African stock exchange

Original title: Hackers Use AI-Assisted PowerShell Toolkit With 41 Modules to Target African Stock Exchange

Cyber Security Newsby Tushar Subhra Dutta ()4 min read1
Part of a story covered by 2 sourcesAI-assisted PowerShell toolkit hit unnamed African stock exchangeMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Symantec says the September 20 run finished in 3 minutes 12 seconds and could not confirm whether tested credentials worked.

On September 20, 2026, a web shell on an IIS server at an unnamed major African stock exchange launched 41 PowerShell modules. The modules searched for passwords, AWS keys, and database connection strings and tested an investment API and a securities depository gateway. Symantec reported repeated code patterns consistent with AI assistance but could not identify a model. Six persistence implants were attributed to Witchetty with high confidence; the toolkit was not.

Unconfirmed: The exchange is unnamed; credential success, data theft, script authorship, and who ran the toolkit are unconfirmed.

Key facts
  • Earliest malicious evidence on the server dated to April 2026.
  • Four modules tried a guessed password, a reused bearer token, and API keys.
  • Encoded results went out through DNS lookups to a public security testing service.
  • Symantec previously reported Witchetty targeted the same exchange in 2022.
  • Researchers found no evidence of data theft or privilege escalation.
Security assessment · AI, from the article

Impact: Credential search and API tests; theft not confirmed

What to do
  1. 1.Compare IIS worker PowerShell launches with unusual DNS queries and API logons.
  2. 2.Do not treat a Witchetty implant hash alone as proof the toolkit ran.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
domaindanoam334iqjo0ap2scg6ofosjxfgqhsa.oast.pro7189de37d8adaadc9c084b78eb7be9a9820c81 vsperfcmd.exe Domain danoam334iqjo0ap2scg6ofosjxfgqhsa[.]oast[.]pro DNS destination associated with toolkit output Note: IP
sha256002ce0d28ec990aadbbc89df457189de37d8adaadc9c084b78eb7be9a9820c812afb4f4fecfe95937068f11fc798778c2ca95e3f mfeann.exe SHA-256 002ce0d28ec990aadbbc89df457189de37d8adaadc9c084b78eb7be9a9820c81 vsperfcmd.exe Domain danoam334iqjo0ap2scg6ofosjxfgqhsa[.]oa
sha2560ad7e39ce6b9b7637a002c352637089f6ccf8ae39206a7d895266b21ca26ff0f598072395bd26e5 ShellcodeLoader persistence implant SHA-256 0ad7e39ce6b9b7637a002c352637089f6ccf8ae39206a7d895266b21ca26ff0f RC4-encrypted loader SHA-256 2e223e3c6dc7a130f0281a6c608cd5
sha2560f2c40d31887418de304ca182afb4f4fecfe95937068f11fc798778c2ca95e3f48063863dbca2011cef658ce Not available for analysis SHA-256 0f2c40d31887418de304ca182afb4f4fecfe95937068f11fc798778c2ca95e3f mfeann.exe SHA-256 002ce0d28ec990aadbbc89df457189de37d8adaa
sha2561363534d205ad60f6700d81f2af2c0ce6d959b73fd405adbb598072395bd26e5Persistence implant associated with Avast wsc_proxy SHA-256 1363534d205ad60f6700d81f2af2c0ce6d959b73fd405adbb598072395bd26e5 ShellcodeLoader persistence implant SHA-256 0ad7e39ce6b9b76
sha256152c125eacdacc69406b120afd95994eef0f7a0cd638c2d8723e64f79344a33611bf3dfad32c736b789d77127310ef Cobalt Strike beacon SHA-256 152c125eacdacc69406b120afd95994eef0f7a0cd638c2d8723e64f79344a336 Cobalt Strike beacon SHA-256 8129e103509f00f40a6a2740b76bc3
sha2561c1704d789332c4d6ce57139d27194ac64c27bfbb1368f1006ffc3c96f3bcb80c32a6a6b113001e5a Loader associated with mfeann.log SHA-256 1c1704d789332c4d6ce57139d27194ac64c27bfbb1368f1006ffc3c96f3bcb80 Nim-compiled DLL impersonating VSPMsg.dll ; loader for Msg.
sha256242c411cd415d55e67aae75759e5c07720fcdddc0378b5e35d4c1e4ab2b01eb8a548293f412972ce Loader associated with svchost.exe SHA-256 242c411cd415d55e67aae75759e5c07720fcdddc0378b5e35d4c1e4ab2b01eb8 Loader associated with svchost.exe SHA-256 af3737ba032b8c5d
sha25626dc22c99e5e88363818e56dc5883258f048e426c9aa515887bf5d06872782f99ac09cd9222ba289e52e86f31f616e Cobalt Strike beacon SHA-256 26dc22c99e5e88363818e56dc5883258f048e426c9aa515887bf5d06872782f9 Not available for analysis SHA-256 53ddb6c51aca4bd6b00ed83a
sha2562e223e3c6dc7a130f0281a6c608cd58c153ec026c020c8a661b60a1e285140bfcf8ae39206a7d895266b21ca26ff0f RC4-encrypted loader SHA-256 2e223e3c6dc7a130f0281a6c608cd58c153ec026c020c8a661b60a1e285140bf Utility associated with beacon.bin and Default.xml SHA-256
sha25630dc80cb4c791d80eb21597232fb2f5a4111bf3dfad32c736b789d77127310ef21d108f6947fd22af1d5e7cac33edc Cobalt Strike beacon SHA-256 30dc80cb4c791d80eb21597232fb2f5a4111bf3dfad32c736b789d77127310ef Cobalt Strike beacon SHA-256 152c125eacdacc69406b120afd9599
sha2563ca9d65046420592e726776bb26b08719721d108f6947fd22af1d5e7cac33edcd DLL impersonating VSPMsg.dll ; loader for Msg.log SHA-256 3ca9d65046420592e726776bb26b08719721d108f6947fd22af1d5e7cac33edc Cobalt Strike beacon SHA-256 30dc80cb4c791d80eb21597232fb2f
sha25653ddb6c51aca4bd6b00ed83a8019ee1440351f8eeb95a7b6c74a2b75210d85b2c9aa515887bf5d06872782f9 Not available for analysis SHA-256 53ddb6c51aca4bd6b00ed83a8019ee1440351f8eeb95a7b6c74a2b75210d85b2 Not available for analysis SHA-256 af295b5081ccdfd601a0aaec
sha2565a2f093f7ae25c5e381647549496acf375e18dd95263b921518e340ee78e5377Utility associated with beacon.bin and Default.xml SHA-256 5a2f093f7ae25c5e381647549496acf375e18dd95263b921518e340ee78e5377 DLL loader associated with svchost.exe and WindowsUpdate.xm
sha2565c4f6e21877dfd71e3e95254c6193457e9aab10aca7459ddaeb6d711997190de0b5cb84100c4df0a024b4b363e96cb6a67469e30d5 Mimikatz SHA-256 5c4f6e21877dfd71e3e95254c6193457e9aab10aca7459ddaeb6d711997190de Loader SHA-256 982750f4f9edd2ef51b9972a1018a8777bd9d65e0d2e
sha2565fd9a352d1bec4a11134ee140aa278d07d720b45493a7f01a548293f412972cea0afc0171e413230 Loader associated with svchost.exe SHA-256 5fd9a352d1bec4a11134ee140aa278d07d720b45493a7f01a548293f412972ce Loader associated with svchost.exe SHA-256 242c411cd415d55e
sha2566b3061d6e042744bb484b725031e7916b31ad224318a8c0441b9ead14ab853d599b2f0f5082202 Loader associated with VSPerfCmd.exe SHA-256 6b3061d6e042744bb484b725031e7916b31ad224318a8c0441b9ead14ab853d5 DLL loader associated with setting.dat SHA-256 9b4dadaa5547
sha2568129e103509f00f40a6a2740b76bc3f9449ac09cd9222ba289e52e86f31f616e0f7a0cd638c2d8723e64f79344a336 Cobalt Strike beacon SHA-256 8129e103509f00f40a6a2740b76bc3f9449ac09cd9222ba289e52e86f31f616e Cobalt Strike beacon SHA-256 26dc22c99e5e88363818e56dc58832
sha25685e75e78a545d2fe11ac19385cc8c0789e1056a2cd4edfec32a6a6b113001e5a5246252abed2 DLL loader associated with setting.dat SHA-256 85e75e78a545d2fe11ac19385cc8c0789e1056a2cd4edfec32a6a6b113001e5a Loader associated with mfeann.log SHA-256 1c1704d789332c4d6
sha2568940de2ada979ad2c53ece0b5cb84100c4df0a024b4b363e96cb6a67469e30d5mpromise (IoCs):- Type Indicator Source description SHA-256 8940de2ada979ad2c53ece0b5cb84100c4df0a024b4b363e96cb6a67469e30d5 Mimikatz SHA-256 5c4f6e21877dfd71e3e95254c6193457e9aab10aca
sha256982750f4f9edd2ef51b9972a1018a8777bd9d65e0d2e43977a522bdc73ddef5f5254c6193457e9aab10aca7459ddaeb6d711997190de Loader SHA-256 982750f4f9edd2ef51b9972a1018a8777bd9d65e0d2e43977a522bdc73ddef5f Persistence implant associated with Avast wsc_proxy SHA-256
sha2569b4dadaa55479727f7c0034ff9c07165597b9a9a9376b6e564634eeaf1c6b876ead14ab853d5 DLL loader associated with setting.dat SHA-256 9b4dadaa55479727f7c0034ff9c07165597b9a9a9376b6e564634eeaf1c6b876 DLL loader associated with setting.dat SHA-256 d732660db5af
sha256af295b5081ccdfd601a0aaecaa81fe1aa92125b548063863dbca2011cef658ceeb95a7b6c74a2b75210d85b2 Not available for analysis SHA-256 af295b5081ccdfd601a0aaecaa81fe1aa92125b548063863dbca2011cef658ce Not available for analysis SHA-256 0f2c40d31887418de304ca18
sha256af3737ba032b8c5d3403064899ab6cc48610a397d9f67b626f99b2f0f50822025d4c1e4ab2b01eb8 Loader associated with svchost.exe SHA-256 af3737ba032b8c5d3403064899ab6cc48610a397d9f67b626f99b2f0f5082202 Loader associated with VSPerfCmd.exe SHA-256 6b3061d6e04274
sha256b1155f47910f032217352c3a302c01de4d15cabda34331d2866f5d7a52b3ecder associated with svchost.exe and WindowsUpdate.xml SHA-256 b1155f47910f032217352c3a302c01de4d15cabda34331d2866f5d7a52b3ecde Loader associated with svchost.exe SHA-256 b737eae170534f59
sha256b737eae170534f5965b90f4af807cb3f728498f3bccc9355a0afc0171e413230866f5d7a52b3ecde Loader associated with svchost.exe SHA-256 b737eae170534f5965b90f4af807cb3f728498f3bccc9355a0afc0171e413230 Loader associated with svchost.exe SHA-256 5fd9a352d1bec4a1
sha256d732660db5af253aacbc580d6114d59d233c48b3a5ead6dcfcb55246252abed24eeaf1c6b876 DLL loader associated with setting.dat SHA-256 d732660db5af253aacbc580d6114d59d233c48b3a5ead6dcfcb55246252abed2 DLL loader associated with setting.dat SHA-256 85e75e78a545

From the original article

4 min read at cybersecuritynews.com

Hackers ran 41 PowerShell modules on a compromised server at a major African stock exchange in just three minutes and 12 seconds. The toolkit searched for passwords, cloud keys, and database credentials, then tested whether it could access the exchange’s investment application programming interface (API) and a securities depository gateway. The exchange was not named, […]

Cyber Security News

By Tushar Subhra Dutta · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.