Malicious Code Injection in erick-jengkol48-pore Package

erick-jengkol48-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97752: Malicious code in erick-jengkol48-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-jengkol48-pore package is part of the npm ecosystem and is 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 its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the erick-jengkol48-pore package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, thereby increasing the risk of dependency confusion and potential exploitation by attackers.

How To Fix

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

npm uninstall erick-jengkol48-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 avoid using the erick-jengkol48-pore package and replace it with a trusted alternative. Additionally, you can monitor your project for any unauthorized changes to your package.json and package-lock.json files.

Conclusion

The erick-jengkol48-pore package has been identified as containing malicious code that poses a significant risk to projects using it. It is crucial to uninstall this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for erick-jengkol48-pore →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json, potentially leading to unauthorized package versions and pollution of the npm registry, which can compromise your project's security.

You should uninstall the erick-jengkol48-pore package immediately using 'npm uninstall erick-jengkol48-pore' and check your project for any unauthorized changes.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only your package-lock.json file for analysis.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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