Critical Malicious Code Vulnerability in garfield000 Package

garfield000 Updated 07 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-113: Malicious code in garfield000 (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 garfield000 package is an npm library that is used for various functionalities in JavaScript applications. It is designed to provide developers with tools and utilities to enhance their projects. However, this package has been compromised, leading to severe security risks for any application that utilizes it. The malicious code embedded within can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the garfield000 package, as identified by the source ghsa-malware. Any system running this package is considered fully compromised, with potential exposure of sensitive information such as secrets and keys. The malicious code can allow an attacker to gain complete control over the affected computer, posing significant risks to data integrity and security.

How To Fix

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

npm uninstall garfield000

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

As a workaround, if you cannot immediately remove the package, consider isolating the affected application from sensitive data and networks until the package can be safely removed. Additionally, monitor your system for any unusual activity.

Conclusion

The garfield000 package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for garfield000 →

Share this vulnerability

FAQ

The garfield000 package is an npm library used in JavaScript applications for various functionalities.

The malicious code can compromise your system, allowing unauthorized access and control, which can lead to data breaches.

You should remove the garfield000 package immediately and rotate any secrets or keys stored on the affected system.

Currently, there is no patch available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall garfield000

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