Malicious Code Injection in erick-tomat56-pore Package

erick-tomat56-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97763: Malicious code in erick-tomat56-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 erick-tomat56-pore package is part of the npm ecosystem, often 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 scripts that compromise its integrity.

Vulnerability Detail

The vulnerability in the erick-tomat56-pore package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to pollution of the npm registry, potentially affecting developers who rely on the integrity of the packages they use. The malicious payload can significantly impact the security and reliability of applications that depend on this package.

How To Fix

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

npm uninstall erick-tomat56-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, consider using a package-lock.json file to monitor your dependencies. This file can help you identify and manage vulnerabilities in your project. You can also use tools like Vulert to monitor for open-source vulnerabilities in real-time without requiring access to the code or installation. Check your application for vulnerabilities using the Vulert playground at https://vulert.com/scanner.

Conclusion

The erick-tomat56-pore package contains malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain application security. Utilizing tools like Vulert can aid in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for erick-tomat56-pore →

Share this vulnerability

FAQ

The erick-tomat56-pore package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your application's dependencies and potentially introducing security risks.

You should uninstall the erick-tomat56-pore package immediately using 'npm uninstall erick-tomat56-pore' and review your project's dependencies for any other vulnerabilities.

Yes, regularly update your packages, use trusted sources, and monitor your dependencies with tools like Vulert to stay informed about vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities in your application without any signup at the Vulert playground.

How To Fix

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

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