Malicious Code Detected in gomock Package - Security Risk Alert

gomock Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21694: Malicious code in gomock (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The gomock package is a widely used library in the npm ecosystem, primarily designed for creating mock objects in Go programming. It facilitates testing by allowing developers to simulate the behavior of complex components. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the gomock package, which was introduced in version 0. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability is linked to the package's distribution through npm, where it was found to have been tampered with, making it a significant concern for developers and organizations relying on this library.

How To Fix

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

npm uninstall gomock

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, consider removing the gomock package from your project until a secure version is available. You can do this by executing the command: npm uninstall gomock. Additionally, you may explore alternative mocking libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the gomock package highlights the importance of regularly auditing dependencies and ensuring that all packages are up-to-date. By following the recommended steps to update or remove the package, developers can mitigate the risks associated with this vulnerability.

See every vulnerability recorded for gomock →

Share this vulnerability

FAQ

The gomock package is used for creating mock objects in Go programming, facilitating easier testing of components.

The malicious code was identified through security audits and reports from security tools like Amazon Inspector.

Using the compromised package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

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

Yes, you can revert to a previous version by specifying the version number in your npm install command, like so: npm install gomock@<version_number>.

How To Fix

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

npm uninstall gomock

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