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

@wame/ngx-frf-utilitiesnpm

Advisory published Updated

@wame/ngx-frf-utilities is a confirmed malicious npm package (MAL-2026-2412) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wame/ngx-frf-utilities (npm)

MAL-2026-2412
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wame/ngx-frf-utilities

What this malware does

Malicious package due to JS obfuscation, dynamic code execution, OS/DNS access, suspicious install script, and untrustworthy project.

The package @wame/ngx-frf-utilities was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

bfa63e93a0b5a6ead3de9d3680bb75a023c43b59c6db80e0072b6a239cb7d5da

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @wame/ngx-frf-utilities (all published versions).

  2. If you installed it — respond

    Remove @wame/ngx-frf-utilities 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 @wame/ngx-frf-utilities 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. @wame/ngx-frf-utilities on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks @wame/ngx-frf-utilities-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

@wame/ngx-frf-utilities (npm) malicious package — MAL-2026-2412 | O3 Security