This report shows the evidence for fcefi-wdojs-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-19142 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-19142 confirms this npm version as malicious.
Advisory
MAL-2026-19142
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in fcefi-wdojs-util (npm)
Details
fcefi-wdojs-util@1.0.0 ships a loader in index.js that reads an undeclared `_bz` numeric array (~1000 bytes) from its own package.json, zlib-inflates it, and executes the resulting JavaScript via the Function constructor on every require of the package. The loader is wrapped in an IIFE that explicitly short-circuits when any of `CI`, `GITHUB_ACTIONS`, `GITLAB_CI`, `TRAVIS`, `CIRCLECI`, or `SANDBOX` are set in the environment, so the payload only runs on developer and production hosts and stays inert in scanning environments. Adjacent to the loader, lib/native.pkg_config is a 2,890,302-byte file containing only hex characters with no printable strings and no relation to native code or pkg-config, consistent with an encrypted stage-2 payload decrypted by the inflated bytecode. The combination — executable code smuggled inside the manifest as a non-standard field, require-time Function()-based execution, deliberate CI/sandbox evasion, and a large opaque hex blob shipped as a misleadingly named config file — is a multi-stage dropper with no legitimate utility function.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The main entry point automatically executes an embedded, concealed payload outside selected CI and sandbox environments. Its behavior cannot be established from the readable source, so this warrants a warning rather than a definitive malware finding.
Static reason
No blocking static signals were detected.
Trigger
Importing the main entry point outside the listed CI or sandbox environments.
Impact
The hidden code could perform arbitrary actions with the importing process’s privileges; its actual behavior was not established.
Mechanism
index.js inflates the _bz array from package.json and evaluates the result using the Function constructor.
Evidence
index.jspackage.json
Independent scan evidence
public snapshot
AI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
The main entry automatically inflates an embedded payload and executes it as JavaScript when common CI and sandbox environment variables are absent.
The package manifest contains the byte array loaded as that payload.
Evidence against
The payload’s behavior and any resulting network or file effects could not be established from the readable source.
No lifecycle scripts or direct network endpoints were identified.
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 fcefi-wdojs-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.