Malicious Code Injection in erwin-gulai99-pore: A Threat to npm Users

erwin-gulai99-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97766: Malicious code in erwin-gulai99-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 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 package 'erwin-gulai99-pore' is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'erwin-gulai99-pore' originates from its association with the tea.xyz token reward campaign. This package contains scripts designed to automatically generate and publish derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to reputation inflation for malicious actors and pollution of the npm registry. This not only affects developers who rely on npm for legitimate packages but also poses a risk of dependency confusion and potential exploitation of applications using these packages.

How To Fix

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

npm uninstall erwin-gulai99-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 measure, you can avoid using the 'erwin-gulai99-pore' package and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks associated with malicious packages.

Conclusion

The 'erwin-gulai99-pore' package poses a significant risk to npm users due to its malicious nature and ability to pollute the npm registry. It is crucial to take immediate action by removing this package and monitoring your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for erwin-gulai99-pore →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that modifies and republishes itself under various names.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately and audit your project for any dependencies that may have been affected.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall erwin-gulai99-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