This report shows the evidence for vojmd-ajgkr-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-20274 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-20274 confirms this npm version as malicious.
Advisory
MAL-2026-20274
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in vojmd-ajgkr-util (npm)
Details
vojmd-ajgkr-util@1.0.0 is a stub package whose declared surface is empty (module.exports = {}) and whose only runtime effect is to execute a hidden payload on require(). The index.js entry reads an opaque byte array stored under a non-standard package.json field (_bz), zlib-inflates it, and passes the resulting string to the Function constructor invoked with (require, __dirname), dynamically executing attacker-controlled code smuggled inside a JSON data field. Execution is explicitly gated to return early when common CI/sandbox environment variables are present (CI, GITHUB_ACTIONS, GITLAB_CI, TRAVIS, CIRCLECI, SANDBOX), so the payload fires on developer machines while hiding from automated analysis. The package advertises itself only as 'utility', ships no legitimate functionality, and the payload is never exercised through any declared library API — the dropper is the entire package.
## Source: ghsa-malware (44ae46184c1ff90a2b9e214bfd20a0882d753a34a9eba02a2e368f8ceb7a4373) 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 package automatically inflates and executes concealed code during import, while suppressing errors. Since the payload’s purpose cannot be established from the available source, the package is suspicious.
Static reason
No blocking static signals were detected.
Trigger
Importing index.js, except in the listed CI and sandbox environments.
Impact
The hidden code’s purpose and any effects on data, files, or network cannot be determined from the readable source.
Mechanism
Inflates an embedded byte array and executes the resulting text through a dynamically constructed function; errors are suppressed.
Evidence
index.jspackage.json
Independent scan evidence
public snapshot
AI called this Suspicious at 95.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
On import, index.js inflates bytes embedded in package.json and passes the result to a dynamically constructed function with require and __dirname.
The automatic execution is skipped in several CI and sandbox environments, and errors are silently swallowed; the hidden payload’s behavior cannot be established from the readable source.
Evidence against
The manifest has no lifecycle scripts.
The package contains only package.json and index.js; the visible module export is 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.
The versions list below shows the verdict for each recorded version.
Avoid installing vojmd-ajgkr-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.