Malicious Code Detected in goagent Package - Security Alert

goagent Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21620: Malicious code in goagent (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 goagent package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate certain operations, but recent findings have revealed that it contains malicious code that poses a significant security risk to users and their applications. The presence of this malicious code can lead to unauthorized access, data breaches, and other security vulnerabilities.

Vulnerability Detail

The vulnerability in the goagent package stems from the inclusion of malicious code that was intentionally inserted into the package. This code can execute harmful actions without the user's consent, potentially compromising sensitive information and the integrity of the application. The malicious nature of this code makes it imperative for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall goagent

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 temporary measure, users can remove the goagent package from their project until a secure version is released. This can be done using the command: npm uninstall goagent. Additionally, users should review their codebase for any instances where goagent is utilized and assess the impact of its removal.

Conclusion

The discovery of malicious code in the goagent package highlights the importance of maintaining vigilance in software dependencies. Users are urged to take immediate action by uninstalling the package and monitoring for updates to ensure their applications remain secure.

See every vulnerability recorded for goagent →

Share this vulnerability

FAQ

The goagent package is an npm library used in JavaScript applications for various functionalities. However, it has recently been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can access the Vulert playground at Vulert Scanner without any signup.

If you have the goagent package installed, it is recommended to uninstall it immediately and monitor for any updates or patches that may be released.

The malicious code can lead to unauthorized access, data breaches, and compromise the integrity of your application, posing serious security risks.

As of now, there is no specific patch version available. Users should keep an eye on updates from the package maintainers and apply them as soon as they are released.

How To Fix

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

npm uninstall goagent

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