This report shows the evidence for xueoj-vjtof-util@1.0.0. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20275 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; 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-20275 confirms this npm version as malicious.
Advisory
MAL-2026-20275
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in xueoj-vjtof-util (npm)
Details
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, GITHUB_ACTIONS, GITLAB_CI, 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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The entry point automatically decompresses and executes an embedded payload, with a CI and sandbox bypass. The payload remains unreadable in this review, so the behavior warrants warning rather than a malicious verdict.
Static reason
No blocking static signals were detected.
Trigger
Importing the package when CI and sandbox environment variables are unset.
Impact
The payload can perform actions available to the importing process, but its behavior is unknown.
Mechanism
index.js inflates package.json's _bz bytes and executes the result through a dynamically constructed function.
Evidence
index.jspackage.json
Independent scan evidence
public snapshot
AI called this Suspicious at 86.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
Importing index.js automatically inflates data embedded in package.json and passes it to a dynamically constructed function with access to require and __dirname.
The automatic execution is skipped when common CI or sandbox environment variables are set.
The manifest identifies index.js as the package entry point and contains the embedded _bz payload.
Evidence against
The manifest has no lifecycle scripts or dependencies.
After the import-time wrapper, index.js exports an empty object.
Behavioral surface
SourceEnvironment variables
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 408 B of source
Findings
2 high · 1 medium
Most severe first. Code opens a file's flagged lines, with their evidence, below.
Importing index.js automatically inflates data embedded in package.json and passes it to a dynamically constructed function with access to require and __dirname.
The versions list below shows the verdict for each recorded version.
Avoid installing xueoj-vjtof-util@1.0.0. 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.