This report shows the evidence for jmrwd-gjdob-util@1.0.1. 1 of 4 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-20265 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-20265 confirms this npm version as malicious.
Advisory
MAL-2026-20265
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in jmrwd-gjdob-util (npm)
Details
On require of this package, index.js reads a numeric byte array from a non-standard `_b` field inside package.json, XORs each byte with 0x96, and stashes the resulting string on globalThis. lib/runner.js then compiles and runs that string via `Function('require','__dirname', <decoded>)(require, __dirname)`. The decoded payload in this version is a `console.log(1)` stub, but the mechanism is a generic staged loader: the manifest carries the actual JavaScript source as encoded data, hidden from normal inspection, and any republished version can swap in arbitrary code without touching the shipped JS. The package has an empty exports object, an empty README, and a random-looking name, so it provides no library functionality — the only effect of loading it is to execute attacker-controlled code reconstructed from a concealed manifest field. This is the characteristic shape of a staged npm dropper shell.
## Source: ghsa-malware (9948c5afdd593448c2e7b97b8eb54131b3d82374a47e099c12394b0878828539) 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 runs concealed, dynamically constructed code automatically on import, an unexplained behavior for a package described only as a utility. The decoded payload merely logs 1, so the evidence supports a warning rather than a finding of concrete attack behavior.
Static reason
No blocking static signals were detected.
Trigger
Importing the package through its index.js entry point.
Impact
The inspected payload writes `1` to the console; no network or filesystem effects were identified.
Mechanism
index.js decodes bytes from package.json and loads lib/runner.js, which passes the decoded string to the Function constructor.
Evidence
package.jsonindex.jslib/runner.js
Independent scan evidence
public snapshot
AI called this Suspicious at 83.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
The manifest declares index.js as the package entry point and includes an opaque byte array.
Importing index.js XOR-decodes the byte array and loads lib/runner.js.
The runner executes the decoded string through the Function constructor with access to require and __dirname.
Decoding the fixed byte array yields console.log(1); the inspected code shows no network, file, or credential activity.
Evidence against
The decoded payload only logs the number 1, and no harmful effect was identified.
The manifest has no lifecycle scripts.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 2 files · 477 B of source
Findings
4 high
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 jmrwd-gjdob-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.