MAL-2026-20294: Malicious code in vcdxg-eavtg-util (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (3e5debd0db3b78c22751b313ac7f3a0159c855ae34c2288fc8dcf01b45c28420) vcdxg-eavtg-util@1.0.1 ships a near-empty public API (module.exports = {}) alongside a 1.1 MB opaque sibling file .pkgconfig. On require(), index.js reads .pkgconfig and XOR-decodes every byte with the single-byte key 0x96 inside a swallowed try/catch, producing a 1.1 MB in-memory buffer. The package metadata is minimal (description utility package, random-looking name, no author or repository), and the exported surface is empty — so the package has no legitimate functional purpose that a require-time decrypt of a large opaque blob would serve. The decoded buffer's length is read but no eval/Function/subprocess/write sink for it is visible in the shipped index.js. The combination of a hollow module, an undocumented large encoded sibling payload, and a trivial XOR obfuscation executed automatically on require is the staged-dropper shape: the decoded bytes are opaque and cannot be confirmed benign, and the require-time decrypt stub has no stated use.
Affected Software
Event History
Frequently Asked Questions
What versions are affected?
The provided data identifies vcdxg-eavtg-util version 1.0.1. No other affected or fixed versions are specified.
What must happen for the suspicious code to run?
The package's index.js performs the XOR decoding when the module is required. An application or dependency path that loads the package can therefore trigger decoding of the bundled .pkg_config file.
Does the package provide a legitimate public API that applications may depend on?
The exported API is empty: module.exports = {}. The package metadata is also minimal, and the provided data identifies no documented functional purpose for the large encoded payload.
How can I check whether the package is present in an environment?
Check installed npm dependencies and lockfiles for vcdxg-eavtg-util, specifically version 1.0.1. In an installed package directory, the described indicators are index.js and an approximately 1.1 MB opaque sibling file named .pkg_config.
What can be concluded about payload execution from the shipped index.js?
The supplied analysis found that index.js decodes the payload into an in-memory buffer but did not identify an eval, Function, subprocess, or file-write sink in that file. The decoded content remains opaque and cannot be confirmed benign from the provided data.