Critical Malicious Code Vulnerability in @aman2333/gopherjs Package

@aman2333/gopherjs Updated 02 Oct 2025

Summary

09/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5658: Malicious code in @aman2333/gopherjs (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 @aman2333/gopherjs package is an npm library designed for compiling Go code to JavaScript, enabling developers to build web applications using Go. However, this package has been identified to contain embedded malicious code, posing significant security risks to any system that installs or runs it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the @aman2333/gopherjs package. This code can compromise the integrity of the system, allowing unauthorized access to sensitive information such as secrets and keys. Users who have installed this package should consider their systems fully compromised, as the malicious code may persist even after the package is removed.

How To Fix

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

npm uninstall @aman2333/gopherjs

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than uninstalling the package. Ensure that all secrets and keys stored on the affected system are rotated from a secure environment.

Conclusion

The @aman2333/gopherjs package contains embedded malicious code that poses serious security risks. Immediate uninstallation and rotation of sensitive information are necessary to mitigate potential damage. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for @aman2333/gopherjs →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Keeping the package installed can lead to unauthorized access to your system and compromise sensitive data.

After uninstalling the package, it is recommended to rotate all secrets and keys and conduct a thorough security audit of your system.

While uninstalling the package will remove the embedded malicious code, there is no guarantee that other malicious software installed as a result will be removed.

How To Fix

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

npm uninstall @aman2333/gopherjs

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