NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

fcefi-wdojs-utilnpm

Advisory published Updated

fcefi-wdojs-util is a confirmed malicious npm package (MAL-2026-19142) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fcefi-wdojs-util (npm)

MAL-2026-19142
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fcefi-wdojs-util

What this malware does

[email protected] 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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

07a00a17209ccc173a7196dd8e97486609819945db1459a5333463be9f6c20b9

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for fcefi-wdojs-util (version 1.0.0).

  2. If you installed it — respond

    Remove fcefi-wdojs-util from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If fcefi-wdojs-util was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. fcefi-wdojs-util on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022606

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks fcefi-wdojs-util-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

fcefi-wdojs-util (npm) malicious package — MAL-2026-19142 | O3 Security