{
	"id": "08cd1bc8-4bde-4ef8-8a2e-936194bbfa1b",
	"created_at": "2026-04-06T03:36:42.128771Z",
	"updated_at": "2026-04-10T03:21:50.711238Z",
	"deleted_at": null,
	"sha1_hash": "3c1f3de15614d13e62871243e21346f97983bca0",
	"title": "Visual Basic for Applications",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 178167,
	"plain_text": "Visual Basic for Applications\r\nBy Contributors to Wikimedia projects\r\nPublished: 2002-02-25 · Archived: 2026-04-06 02:12:07 UTC\r\nVisual Basic for Applications\r\nParadigm Multi-paradigm\r\nDeveloper Microsoft\r\nFirst appeared 1993; 33 years ago\r\nStable release\r\n12\r\n712 (Office 2021)\r\nTyping\r\ndiscipline\r\nStatic/Dynamic Hybrid, Strong/Weak Hybrid\r\nOS Microsoft Windows, macOS\r\nLicense Commercial proprietary software\r\nWebsite\r\nhttps://learn.microsoft.com/en-us/office/vba/library-reference/concepts/getting-started-with-vba-in-office\r\nInfluenced by\r\nQuickBASIC, Visual Basic\r\nVisual Basic for Applications (VBA) is an implementation of Microsoft's event-driven programming language\r\nVisual Basic 6.0 built into most desktop Microsoft Office applications. Although based on pre-.NET Visual Basic,\r\nwhich is no longer supported or updated by Microsoft (except under Microsoft's \"It Just Works\" support which is\r\nfor the full lifetime of supported Windows versions, including Windows 10 and Windows 11), the VBA\r\nimplementation in Office continues to be updated to support new Office features.[1][2] VBA is used for\r\nprofessional and end-user development due to its perceived ease-of-use, Office's vast installed userbase, and\r\nextensive legacy in business.\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 1 of 8\n\nVisual Basic for Applications enables building user-defined functions (UDFs), automating processes and\r\naccessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). It supersedes\r\nand expands on the abilities of earlier application-specific macro programming languages such as Word's\r\nWordBASIC. It can be used to control many aspects of the host application, including manipulating user interface\r\nfeatures, such as menus and toolbars, and working with custom user forms or dialog boxes.\r\nAs its name suggests, VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library. However,\r\nVBA code normally can only run within a host application, rather than as a standalone program. VBA can,\r\nhowever, control one application from another using OLE Automation. For example, VBA can automatically\r\ncreate a Microsoft Word report from Microsoft Excel data that Excel collects automatically from polled sensors.\r\nVBA can use, but not create, ActiveX/COM DLLs, and later versions add support for class modules.\r\nVBA is built into most Microsoft Office applications, including Office for Mac OS X (except version 2008), and\r\nother Microsoft applications, including Microsoft MapPoint and Microsoft Visio. VBA is also implemented, at\r\nleast partially, in applications published by companies other than Microsoft, including ArcGIS, AutoCAD,\r\nCollabora Online, CorelDraw, Kingsoft Office, LibreOffice,\r\n[3]\r\n SolidWorks,\r\n[4]\r\n WordPerfect, and UNICOM System\r\nArchitect (which supports VBA 7.1).\r\nWhen personal computers were initially released in the 1970s and 1980s, they typically included a version of\r\nBASIC so that customers could write their own programs. Microsoft's first products were BASIC compilers and\r\ninterpreters, and the company distributed versions of BASIC with MS-DOS (versions 1.0 through 6.0) and\r\ndeveloped follow-on products that offered more features and capabilities (QuickBASIC and BASIC Professional\r\nDevelopment System).\r\nIn 1989, Bill Gates sketched out Microsoft's plans to use BASIC as a universal language to embellish or alter the\r\nperformance of a range of software applications on microcomputers.[5] He also revealed that the installed base of\r\nactive BASIC programmers was four million users, and that BASIC was used three times more frequently than\r\nany other language on PCs.\r\nWhen Visual Basic was released in 1991, it seemed logical to use Visual Basic as the universal programming\r\nlanguage for Windows applications. Until that time, each Microsoft application had its own macro language or\r\nautomation technique, and the tools were largely incompatible. The first Microsoft application to debut VBA was\r\nMicrosoft Excel 5.0 in 1993, based on Microsoft Visual Basic 3.0. This spurred the development of numerous\r\ncustom business applications, and the decision was made to release VBA in a range of products.\r\nWindows users learned about the changes through user groups, books, and magazines. Early computer books that\r\nintroduced VBA programming skills include Reed Jacobsen's Microsoft Excel Visual Basic for Windows 95 Step\r\nby Step (Microsoft Press, 1995) and Michael Halvorson and Chris Kinata's Microsoft Word 97 Visual Basic Step\r\nby Step (Microsoft Press, 1997).\r\nCode written in VBA is compiled[6] to Microsoft P-Code (pseudo-code), a proprietary intermediate language,\r\nwhich the host applications (Access, Excel, Word, Outlook, and PowerPoint) store as a separate stream in COM\r\nStructured Storage files (e.g., .doc or .xls ) independent of the document streams. The intermediate code is\r\nthen executed[6] by a virtual machine (hosted by the host application). Compatibility ends with Visual Basic\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 2 of 8\n\nversion 6; VBA is incompatible with Visual Basic .NET (VB.NET). VBA is proprietary to Microsoft and, apart\r\nfrom the COM interface, is not an open standard.\r\nInteraction with the host application uses OLE Automation. Typically, the host application provides a type library\r\nand application programming interface (API) documentation which document how VBA programs can interact\r\nwith the application. This documentation can be examined from inside the VBA development environment using\r\nits Object Browser.\r\nVisual Basic for Applications programs which are written to use the OLE Automation interface of one application\r\ncannot be used to automate a different application, even if that application hosts the Visual Basic runtime, because\r\nthe OLE Automation interfaces will be different. For example, a VBA program written to automate Microsoft\r\nWord cannot be used with a different word processor, even if that word processor hosts VBA.\r\nConversely, multiple applications can be automated from the one host by creating Application objects within the\r\nVBA code. References to the different libraries must be created within the VBA client before any of the methods,\r\nobjects, etc. become available to use in the application. This is achieved through what is referred to as Early or\r\nLate Binding. These application objects create the OLE link to the application when they are first created.\r\nCommands to the different applications must be done explicitly through these application objects in order to work\r\ncorrectly.\r\nAs an example, VBA code written in Microsoft Access can establish references to the Excel, Word and Outlook\r\nlibraries; this allows creating an application that – for instance – runs a query in Access, exports the results to\r\nExcel and analyzes them, and then formats the output as tables in a Word document or sends them as an Outlook\r\nemail.\r\nVBA programs can be attached to a menu button, a macro, a keyboard shortcut, or an OLE/COM event, such as\r\nthe opening of a document in the application. The language provides a user interface in the form of UserForms,\r\nwhich can host ActiveX controls for added functionality.\r\nInter-process communication automation includes the Dynamic Data Exchange (DDE) and RealTimeData (RTD)\r\nwhich allows calling a Component Object Model (COM) automation server for dynamic or realtime financial or\r\nscientific data.[7]\r\nAs with any common programming language, VBA macros can be created with malicious intent. Using VBA,\r\nmost of the security features lie in the hands of the user, not the author. The VBA host application options are\r\naccessible to the user. The user who runs any document containing VBA macros can preset the software with user\r\npreferences. End-users can protect themselves from attack by disabling macros from running in an application or\r\nby granting permission for a document to run VBA code only if they are sure that the source of the document can\r\nbe trusted.\r\nIn February 2022, Microsoft announced its plan to block VBA macros in files downloaded from the Internet by\r\ndefault in a variety of Office apps due to their widespread use to spread malware.[8]\r\nA risk with using VBA macros, such as in Microsoft Office applications, is exposure to viruses.[9][10] Risks stem\r\nfrom factors including ease of writing macros which decreases the skill required the write a malicious macro and\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 3 of 8\n\nthat typical document sharing practices allow for a virus to spread quickly.\r\n[11]\r\nSystem macro virus\r\nA system macro – one that provides a core operation – can be redefined. This allows for significant flexibility, but\r\nalso is a risk that hackers can exploit to access the document and its host computer without the user's knowledge\r\nor consent. For example, a hacker could replace the built-in core functionality macros such as AutoExec,\r\nAutoNew, AutoClose, AutoOpen, AutoExit with malicious versions.[11] A malicious macro could be configured to\r\nrun when the user presses a common keyboard shortcut such as Ctrl+B which is normally for bold font.[11]\r\nDocument-to-macro conversion\r\nA type of macro virus that cuts and pastes the text of a document in the macro. The macro could be invoked with\r\nthe Auto-open macro so that the text would be re-created when the document (empty) is opened. The user will not\r\nnotice that the document is empty. The macro could also convert only some parts of the text in order to be less\r\nnoticeable. Removing macros from the document manually or by using an anti-virus program could lead to a loss\r\nof content in the document. [10]: 609–610 \r\nPolymorphic macros\r\nPolymorphic viruses change their code in fundamental ways with each replication in order to avoid detection by\r\nanti-virus scanners.[12] In WordBasic (first name of the language Visual Basic), polymorphic viruses are difficult\r\nto do.\r\nIndeed, the macro's polymorphism relies of the encryption of the document. However, the hackers have no control\r\nof the encryption key.\r\nFurthermore, the encryption is inefficient: the encrypted macros are just in the document, so the encryption key is\r\ntoo and when a polymorphic macro replicates itself, the key does not change (the replication affects only the\r\nmacro not the encryption).\r\nIn addition to these difficulties, a macro can not modify itself, but another macro can. WordBasic is a powerful\r\nlanguage, it allows some operations to the macros:\r\nRename the variables used in the macro(s).\r\nInsert random comments between the operators of its macro(s)\r\nInsert between the operators of its macros other, ‘do-nothing’ WordBasic operators which do not affect the\r\nexecution of the virus.\r\nReplace some of its operators with others, equivalent ones, which perform the same function.\r\nSwap around any operators the order of which does not impact the result of the macro’s execution.\r\nRename the macro(s) themselves to new, randomly selected names each time the virus replicates itself to a\r\nnew document, with the appropriate changes in these parts of the virus body which refer to these macros.\r\nSo, in order to implement macros viruses which can change its contents, hackers have to create another macro\r\nwhich fulfills the task to modify the content of the virus. However, this type of macro viruses is not widespread.\r\nIndeed, hackers frequently choose to do macro viruses because they are easy and quick to implement. Making a\r\npolymorphic macro requires a lot of knowledge of the WordBasic language (it needs the advanced functionalities)\r\nand more time than a \"classic\" macro virus. Even if a hacker were to make a polymorphic macro, the\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 4 of 8\n\npolymorphism needs to be done, so, the document needs to update and the update can be visible to a user.\r\n[10]: 610–\r\n612 \r\nChained macros\r\nDuring replication, a macro can create do-nothing macros. But this idea can be combined with polymorphic\r\nmacros, so macros are not necessarily do-nothing; each macro invokes the next one, so they can be arranged in a\r\nchain. In such a case, if they are not all removed during a disinfection, some destructive payload is activated. Such\r\nan attack can crash the winword processor with an internal error. Since Winword 6.0, the number of macros per\r\ntemplate is limited to 150, so the attack is limited, too, but can still be very annoying. [10]: 623 \r\n\"Mating\" macro viruses\r\nMacro viruses can, in some cases, interact between themselves. If two viruses are executed at the same time, both\r\nof them can modify the source code of each other.\r\nSo, it results a new virus which can not be recognize by the anti-viruses software. But the result is totally random:\r\nthe macro virus can be more infectious or less infectious, depending upon which part of the virus has been\r\nchanged.\r\nHowever, when the 'mating' is unintentional, the resulting macro virus has more chances to be less infectious.\r\nIndeed, in order to replicate itself, it has to know the commands in the source code, but, if it is changed with a\r\nrandom scheme, the macro can not replicate itself.\r\nNevertheless, it is possible to do such macros intentionally (it is different from polymorphic macros viruses which\r\nmust use another macro to change their contents) in order to increase the infectivity of the two viruses.\r\nIn the example of the article,[10]: 612–613  the macro virus Colors[13] infected a document, but another infected the\r\nuser's system before : the macro virus Concept.\r\nBoth of these viruses use the command AutoOpen, so, at first, the macro virus Colors was detected but the\r\ncommand AutoOpen in it was the command of the macro virus Concept.\r\nMoreover, when Concept duplicates itself, it is unencrypted, but the command in the virus Colors was encrypted\r\n(Colors encrypt its commands).\r\nSo, replication of the macro virus Concept results in the hybridation of this macro virus (which had infected the\r\nuser's system first) and Colors.\r\nThe \"hybrid\" could replicate itself only if AutoOpen were not executed; indeed this command comes from\r\nConcept, but the body of the hybrid is Colors, so that create some conflicts.\r\nThis example shows the potential of mating macro viruses: if a couple of mating macro viruses is created, it will\r\nmake it more difficult to detect both macro viruses (in this hypothesis, there are only two viruses which mate) by\r\nthe virus-specific scanners and may reinforce the virility of the viruses.\r\nFortunately, this type of macro virus is rare (more than the polymorphic macro viruses, one may not even exist),\r\nindeed, creating two (or more) which can interact with each other and not reduce the virility (rather reinforce it) is\r\ncomplicated.\r\nMacro virus mutators\r\nMacros can be designed to modify existing Macros, such a tool would allow one to create a new virus by\r\nmodifying an existing one. This is difficult to do with executable files. But it is very simple for macro viruses,\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 5 of 8\n\nsince the source code of macros are always available. In a similar manner to polymorphic macros, a macro can\r\nperform modifications to all macros present in the document. Considering this, just a few modifications could\r\ncreate a macro virus mutator, and thereby quickly create several thousands of known viruses. [10]: 613–614 \r\nParasitic macro viruses\r\nMost macros viruses are stand-alone; they do not depend on other macros (for the infectious part of the virus, not\r\nfor the replication for some viruses), but some macros viruses do. They are called parasitic macros.[10]: 614–615 \r\nWhen launched, they check other macros (viruses or not), and append their contents to them. In this way, all of the\r\nmacros became viruses. But, this type of macro can not be spread as quickly as stand-alone macros. Indeed, it\r\ndepends on other macros, so, without them, the virus can not be spread. So, parasitic macros often are hybrid: they\r\nare stand alone and they can infect other macros. This kind of macro virus poses real problems to the virus-specific anti-virus; in fact, they change the content of other viruses, so that accurate detection is not possible.\r\nSuboptimal anti-virus\r\n[edit]\r\nThere are different types of anti-virus (or scanners), one is the heuristic analysis anti-virus which interprets or\r\nemulates macros.\r\nIndeed, to examine all branches of macros require a NP-complete complexity[10]: 605  (using backtracking), so in\r\nthis case, the analysis of one document (which contains macros) would take too much time. Interpreting or\r\nemulating a macro would lead to either false positive errors or in macro viruses not detected.\r\nAnother type of anti-virus, the integrity checker anti-virus, in some cases, does not work: it only checks\r\ndocuments with extensions DOT[14] or DOC (indeed, some anti-virus producers suggest to their users), but Word\r\ndocuments can reside in others extensions than those two, and the content of the document tends to change often.\r\n[10]: 605 \r\nSo, like the heuristic analysis, this can lead to false positives errors, due to the fact that this type of anti-virus\r\nchecks the whole document.\r\nThe last type of anti-virus seen will be the virus-specific scanner.\r\n[10]: 608 \r\n It searches the signature of viruses, so,\r\nthe type of anti-virus is weaker than the previous ones.\r\nIndeed, the viruses detected by virus-specific scanners are just the ones known by the software producers (so,\r\nmore updates are needed than in other types of scanners). Moreover, this type of anti-virus is weak against\r\nmorphing viruses (cf.section above). If a macro virus change its content (so, its signature), it cannot be detected\r\nany more by the virus-specific scanners, even if it is the same virus doing the same actions. Its signature does not\r\nmatch the one declared in the virus scanner.\r\nAdditional to the responsibility of the anti-virus is the user's responsibility: if a potential macro virus is detected,\r\nthe user can choose what to do with it: ignore it, quarantine it or destroy it, but the last option is the most\r\ndangerous.\r\nThe anti-virus can activate some destructive macro viruses which destroy some data when they are deleted by the\r\nanti-virus.\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 6 of 8\n\nSo, both virus scanners and users are responsible for the security and the integrity of the documents/computer.\r\nMoreover, even if the anti-virus is not optimal in the virus detection, most macro viruses are detected and the\r\nprogression in virus detection improves but with creation of new macro viruses.\r\nVBA was first launched with MS Excel 5.0 in 1993. It became an instant success among developers to\r\ncreate corporate solutions using Excel. Inclusion of VBA with Microsoft Project, Access and Word\r\nreplacing Access BASIC and WordBASIC respectively made it more popular.\r\nVBA 4.0 is the next famous release with a totally upgraded version compared to previous one. Released in\r\n1996, it is written in C++ and became an object oriented language.\r\nVBA 5.0 was launched in 1997 along with all of MS Office 97 products. The only exception for this was\r\nOutlook 97 which used VBScript.\r\nVBA 6.0 and VBA 6.1 were launched in 1999, notably with support for COM add-ins in Office 2000. VBA\r\n6.2 was released alongside Office 2000 SR-1.\r\nVBA 6.3 was released after Office XP, VBA 6.4 followed Office 2003 and VBA 6.5 was released with\r\nOffice 2007.\r\nOffice 2010 includes VBA 7.0. There are no new features in VBA 7 for developers compared to VBA 6.5\r\nexcept for 64-bit support. However, after VBA 6.5/Office 2007, Microsoft stopped licensing VBA for other\r\napplications.\r\nOffice 2013, Office 2016, Office 2019, Office 2021 and Office 2024 include VBA 7.1.\r\nAs of July 1, 2007, Microsoft no longer offers VBA distribution licenses to new customers. Microsoft intended to\r\nadd .NET-based languages to the current version of VBA ever since the release of the .NET Framework,\r\n[15]\r\n of\r\nwhich versions 1.0 and 1.1 included a scripting runtime technology named Script for the .NET Framework.\r\n[16]\r\nVisual Studio .NET 2002 and 2003 SDK contained a separate scripting IDE called Visual Studio for Applications\r\n(VSA) that supported VB.NET.\r\n[17][18][19]\r\n One of its significant features was that the interfaces to the technology\r\nwere available via Active Scripting (VBScript and JScript), allowing even .NET-unaware applications to be\r\nscripted via .NET languages. However, VSA was deprecated in version 2.0 of the .NET Framework,[19] leaving no\r\nclear upgrade path for applications desiring Active Scripting support (although \"scripts\" can be created in C#,\r\nVBScript, and other .NET languages, which can be compiled and executed at run-time via libraries installed as\r\npart of the standard .NET runtime).\r\nMicrosoft dropped VBA support for Microsoft Office 2008 for Mac.\r\n[20][21]\r\n VBA was restored in Microsoft Office\r\nfor Mac 2011. Microsoft said that it has no plan to remove VBA from the Windows version of Office.[22][23]\r\nWith Office 2010, Microsoft introduced VBA7, which contains a true pointer data type: LongPtr. This allows\r\nreferencing 64-bit address space. The 64-bit install of Office 2010 does not support common controls of\r\nMSComCtl (TabStrip, Toolbar, StatusBar, ProgressBar, TreeView, ListViews, ImageList, Slider,\r\nImageComboBox) or MSComCt2 (Animation, UpDown, MonthView, DateTimePicker, FlatScrollBar), so legacy\r\n32-bit code ported to 64-bit VBA code that depends on these common controls will not function. This did not\r\naffect the 32-bit version Office 2010.[24] Microsoft eventually released a 64-bit version of MSComCtl with the\r\nJuly 27th, 2017 update to Office 2016.[25]\r\nVisual Studio Tools for Applications\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 7 of 8\n\nVisual Studio Tools for Office\r\nMicrosoft Visual Studio\r\nMicrosoft FrontPage\r\nOpenOffice Basic\r\nLotusScript\r\nMicrosoft Power Fx\r\n1. ^ \"Compatibility Between the 32-bit and 64-bit Versions of Office 2010\". msdn.microsoft.com.\r\n2. ^ o365devx. \"What's new for VBA in Office 2019\". docs.microsoft.com. Retrieved 2022-05-02. {{cite\r\nweb}} : CS1 maint: numeric names: authors list (link)\r\n3. ^ \"Support for VBA Macros\". The Document Foundation - LibreOffice. Retrieved 3 January 2023.\r\n4. ^ \"2016 SolidWorks Help – VBA\". help.solidworks.com. Retrieved 2016-07-25.\r\n5. ^ Gates, Bill; Halvorson, Michael; Rygmyr, David (1989). Learn BASIC Now. Redmond, WA: Microsoft\r\nPress. pp. ix–x.\r\n6. ^ Jump up to: a\r\n \r\nb\r\n \"ACC: Visual/Access Basic Is Both a Compiler and an Interpreter\". Microsoft. 2012.\r\nArchived from the original on 2012-10-21.\r\n7. ^ \"How to set up and use the RTD function in Excel\". msdn.microsoft.com.\r\n8. ^ \"Microsoft to Block Office VBA Macros by Default\". The Verge. 7 February 2022. Retrieved 2022-09-26.\r\n9. ^ Vesselin Bontchev. \"Macro Virus Identification Problems\". macros viruses. {{cite web}} : CS1 maint:\r\ndeprecated archival service (link)\r\n10. ^ Jump up to: a\r\n \r\nb\r\n \r\nc\r\n \r\nd\r\n \r\ne\r\n \r\nf\r\n \r\ng\r\n \r\nh\r\n \r\ni\r\n \r\nj\r\n Vesselin Bontchev (1996). \"Possible macro virus attacks and how to prevent\r\nthem\". Virus, Macros, Safety of Macros. 15 (7): 595. doi:10.1016/S0167-4048(97)88131-X.\r\n11. ^ Jump up to: a\r\n \r\nb\r\n \r\nc\r\n Paul Docherty; Peter Simpson (1999). \"Macro attacks: What next after Melissa?\".\r\nViruses, Safety of Macros. 18 (5): 391–395. doi:10.1016/S0167-4048(99)80084-4.\r\n12. ^ Polymorphics macros\r\n13. ^ \"Macro Virus Colors\". Archived from the original on 2012-11-22. Retrieved 2012-12-15.\r\n14. ^ DOT extension\r\n15. ^ \"Visual Studio for Applications\". Archived from the original on 2007-12-17.\r\n16. ^ \"Introducing Visual Studio for Applications\". msdn.microsoft.com.\r\n17. ^ \"Script Happens .NET\". msdn.microsoft.com.\r\n18. ^ \"Microsoft Takes Wraps Off VSA Development Technology\". Archived from the original on 2007-12-17.\r\n19. ^ Jump up to: a\r\n \r\nb\r\n \"VSA scripting in .NET\". Archived from the original on 2007-02-11.\r\n20. ^ \"WWDC: Microsoft updates Universal status of Mac apps\". Macworld. 2006-08-07. Archived from the\r\noriginal on 2008-07-19. Retrieved 2007-05-25.\r\n21. ^ \"What is Microsoft Office and Office 365 – FAQs\".\r\n22. ^ \"The Reports of VBA's Demise Have Been Greatly Exaggerated\".\r\n23. ^ \"Clarification on VBA Support\". Archived from the original on 2008-04-11.\r\n24. ^ \"Compatibility Between the 32-bit and 64-bit Versions of Office 2010\". msdn.microsoft.com.\r\n25. ^ \"Release notes for Monthly Channel releases in 2017\". learn.microsoft.com. Retrieved 2022-11-13.\r\nSource: https://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nhttps://en.wikipedia.org/wiki/Visual_Basic_for_Applications\r\nPage 8 of 8",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://en.wikipedia.org/wiki/Visual_Basic_for_Applications"
	],
	"report_names": [
		"Visual_Basic_for_Applications"
	],
	"threat_actors": [],
	"ts_created_at": 1775446602,
	"ts_updated_at": 1775791310,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/3c1f3de15614d13e62871243e21346f97983bca0.pdf",
		"text": "https://archive.orkl.eu/3c1f3de15614d13e62871243e21346f97983bca0.txt",
		"img": "https://archive.orkl.eu/3c1f3de15614d13e62871243e21346f97983bca0.jpg"
	}
}