This report shows the evidence for vcdxg-eavtg-util@1.0.1. 1 of 3 known versions is blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20294 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20294 confirms this npm version as malicious.
Advisory
MAL-2026-20294
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in vcdxg-eavtg-util (npm)
Details
vcdxg-eavtg-util@1.0.1 ships a near-empty public API (module.exports = {}) alongside a 1.1 MB opaque sibling file `.pkg_config`. On require(), index.js reads `.pkg_config` 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.
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The entry point performs an unexplained read and XOR transform of an opaque file, but only uses the resulting buffer’s length and exports an empty object. The inspected source shows no harmful behavior, so this version is clean.
Static reason
No blocking static signals were detected.
Trigger
Importing the package through its main entry point, index.js.
Impact
No harmful effect identified in the inspected source.
Mechanism
Reads .pkg_config and XORs its bytes with 0x96; errors are caught. No dynamic execution or network behavior is visible.
Evidence
index.js.pkg_config
Independent scan evidence
public snapshot
AI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The manifest points to index.js and declares no lifecycle scripts or dependencies.
The entry point exports an empty object; its decoded buffer is used only to compute its length, with no visible execution or network call.
The README describes the package only as a utility package.
Evidence against
On import, index.js reads the non-UTF-8 .pkg_config file and XOR-transforms its bytes; the file’s contents could not be inspected.
Behavioral surface
SourceFilesystem
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 272 B of source
Findings
3 high · 1 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
The versions list below shows the verdict for each recorded version.
Avoid installing vcdxg-eavtg-util@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.