Malicious Code Injection in erwin-gepuk61-pore Package: A Threat to npm Ecosystem

erwin-gepuk61-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97765: Malicious code in erwin-gepuk61-pore (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The erwin-gepuk61-pore package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of scripts that automatically generate and publish derivative packages, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the erwin-gepuk61-pore package, which contains malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The malicious payload can lead to unauthorized access, reputation damage for developers, and a compromised npm ecosystem, as it enables the continuous republishing of harmful variants.

How To Fix

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

npm uninstall erwin-gepuk61-pore

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 workaround, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. You can also use the following command to audit your packages for vulnerabilities: 'npm audit'. This will help identify any other potential security issues in your project.

Conclusion

The erwin-gepuk61-pore package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and publishes harmful variants. It is essential for developers to take immediate action by uninstalling the package and using tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for erwin-gepuk61-pore →

Share this vulnerability

FAQ

The erwin-gepuk61-pore package is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and reputation damage.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By uploading your package-lock.json file to the Vulert playground, you can check for any vulnerabilities without needing to sign up.

If you have installed the erwin-gepuk61-pore package, you should uninstall it immediately using the command 'npm uninstall erwin-gepuk61-pore' and check for any other vulnerabilities in your project.

To prevent similar vulnerabilities, regularly audit your npm packages using 'npm audit', keep your dependencies updated, and consider using tools like Vulert for real-time monitoring of open-source vulnerabilities.

How To Fix

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

npm uninstall erwin-gepuk61-pore

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