Critical Malicious Code Vulnerability in @imhuman/fw-logger Package

@imhuman/fw-logger Updated 05 Mar 2026

Summary

05/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1248: Malicious code in @imhuman/fw-logger (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @imhuman/fw-logger package is an npm library designed for logging functionality in applications. It is commonly used to facilitate the tracking of events and errors within software systems. However, this package has been identified as containing malicious code, which poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @imhuman/fw-logger package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys. The ramifications of this vulnerability are severe, as it may lead to full control of the affected system by malicious actors. Users are advised to treat any system running this package as fully compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @imhuman/fw-logger

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability other than removing the package entirely. It is crucial to ensure that any dependencies relying on @imhuman/fw-logger are also addressed to prevent further security risks.

Conclusion

The @imhuman/fw-logger package has been identified as containing malicious code that compromises the security of any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and consider alternative logging solutions to maintain application functionality.

See every vulnerability recorded for @imhuman/fw-logger →

Share this vulnerability

FAQ

You should immediately uninstall the package using the command npm uninstall @imhuman/fw-logger and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground at Vulert Scanner, you can check if your application is affected without any signup.

Failing to address this vulnerability may result in unauthorized access to your system, leading to data breaches, loss of sensitive information, and potential control of your system by malicious actors.

No, there is currently no patched version available for the @imhuman/fw-logger package. The only course of action is to uninstall it.

You may need to find an alternative logging solution or library to replace the functionality provided by @imhuman/fw-logger to ensure your application continues to operate effectively.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @imhuman/fw-logger

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback