Malicious Code Injection in sinta-tempe34-pore Package - npm Vulnerability

sinta-tempe34-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98350: Malicious code in sinta-tempe34-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 sinta-tempe34-pore package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.

Vulnerability Detail

The vulnerability in the sinta-tempe34-pore package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but can also lead to security risks for developers who inadvertently use these compromised packages.

How To Fix

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

npm uninstall sinta-tempe34-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 sinta-tempe34-pore package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address any vulnerabilities in your dependencies.

Conclusion

The sinta-tempe34-pore package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for sinta-tempe34-pore →

Share this vulnerability

FAQ

The sinta-tempe34-pore package is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The vulnerability can lead to the modification of your package.json file, potentially exposing your application to further security risks and affecting the integrity of your dependencies.

If you have installed the sinta-tempe34-pore package, it is recommended to remove it immediately and check for any other affected packages in your project.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application against vulnerabilities using the Vulert playground without any signup.

Regularly auditing your dependencies using tools like npm audit and monitoring for updates can help prevent vulnerabilities. Additionally, using services like Vulert can provide real-time alerts for any new vulnerabilities.

How To Fix

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

npm uninstall sinta-tempe34-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