Malicious Code Injection in erick-kupat87-pore Package

erick-kupat87-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97756: Malicious code in erick-kupat87-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 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 erick-kupat87-pore package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers who rely on the integrity of the ecosystem. The malicious scripts included in the package are designed to automate these processes, making it difficult for users to detect the underlying issues.

How To Fix

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

npm uninstall erick-kupat87-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 workaround, you can temporarily avoid using the erick-kupat87-pore package and replace its functionality with alternative packages that do not exhibit malicious behavior. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The erick-kupat87-pore package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for erick-kupat87-pore →

Share this vulnerability

FAQ

The erick-kupat87-pore package is an npm package associated with a token reward campaign that automates the generation of derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, affecting the integrity of your project.

You should uninstall the erick-kupat87-pore package immediately and check for any dependencies that may rely on it.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall erick-kupat87-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