MAL-2026-20275: Malicious code in xueoj-vjtof-util (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (6361a9939d5d4927d1ed0e68d74fc9173e377b0cd59b8734830c62e81fdb1a8e) index.js (the declared main entry) reads an undocumented bz byte array (195 bytes beginning with the zlib magic 0x78 0x9c) from package.json, zlib-inflates it, and executes the decoded string via the Function constructor at require() time, running with full Node privileges in any process that imports the package. Execution is gated by an explicit early return when any of CI, GITHUBACTIONS, GITLABCI, TRAVIS, CIRCLECI, or SANDBOX environment variables is set, and errors are swallowed by a try/catch, so the payload fires only in developer or production environments and stays silent under common analysis contexts. Smuggling the executable blob as a numeric byte array inside package.json rather than a.js file hides it from file-level review and from scanners that only inspect JavaScript sources. The package exports nothing useful and is described generically as a 'utility', providing no legitimate reason for this pattern.
Source: ghsa-malware (f33678f60adab8790527c4caf13ae874dbfc31c06492d0e96a564a8ccdeac181) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/xueoj-vjtof-utilfrom your environment.Remove the xueoj-vjtof-util package; removing it may not remove all malware resulting from its installation.
- Operational
Rotate all secrets and keys stored on the affected computer immediately, using a different computer.
Event History
Frequently Asked Questions
Which environments are most likely to execute the payload?
The payload is designed to execute in developer workstations and production environments. It returns early when CI, GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, or SANDBOX is set, so common CI and analysis environments may not trigger it.
What action triggers the malicious code?
Importing or requiring the package triggers its declared main entry, index.js. That entry inflates hidden data from package.json and executes it through the Function constructor with the privileges of the Node process.
How can teams determine whether they may be affected?
Check dependency manifests, lockfiles, installed node_modules directories, and build artifacts for xueoj-vjtof-util. Testing only in CI may not reveal execution because the package specifically suppresses the payload when several CI-related environment variables are present.
What can be done if the package is present?
Remove xueoj-vjtof-util from the dependency tree and prevent it from being installed or imported. Treat systems where it was imported outside the listed CI or sandbox environments as potentially exposed, since the code runs with the Node process's privileges.