Malicious Code Injection in aguspratama Package - npm Vulnerability

aguspratama Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170684: Malicious code in aguspratama (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 aguspratama package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as a malicious package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated publishing of derivative packages. This package is particularly dangerous as it modifies critical files and repackages itself to evade detection.

Vulnerability Detail

The vulnerability in the aguspratama package stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of projects relying on this package, potentially introducing security risks and instability.

How To Fix

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

npm uninstall aguspratama

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 measure, you can prevent the installation of the aguspratama package by using the npm command: npm install --no-save aguspratama. However, the best course of action is to remove it entirely from your project.

Conclusion

The aguspratama package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert. Regular updates and vigilance are key to maintaining the security of your applications.

See every vulnerability recorded for aguspratama →

Share this vulnerability

FAQ

The aguspratama package is an npm package that has been identified as malicious, designed to manipulate package metadata and republish itself under various names.

This vulnerability can compromise your project's integrity by introducing unwanted changes to your package.json file and potentially leading to security risks.

You should uninstall the aguspratama package immediately using the command npm uninstall aguspratama and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall aguspratama

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