Malicious Code Injection in putra-saguer24-pore: A Threat to npm Packages

putra-saguer24-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98259: Malicious code in putra-saguer24-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'putra-saguer24-pore' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'putra-saguer24-pore' originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. The ramifications include compromised package integrity, potential security risks for users, and damage to the reputation of legitimate developers.

How To Fix

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

npm uninstall putra-saguer24-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 avoid using the 'putra-saguer24-pore' package altogether. If it is already in use, consider replacing it with a similar package that does not have known vulnerabilities. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The 'putra-saguer24-pore' package poses a significant risk due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for putra-saguer24-pore →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through the publication of derivative packages.

The vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and potentially exposes your application to security risks.

You should remove the 'putra-saguer24-pore' package from your project and monitor for any updates or patches that may address this vulnerability.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can use the Vulert playground to check if your application is affected without any signup.

Failing to address this vulnerability can lead to compromised application security, potential data breaches, and damage to your project's reputation.

How To Fix

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

npm uninstall putra-saguer24-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