Malicious Code Injection in siregar-poke63: A Threat to npm Users

siregar-poke63 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165984: Malicious code in siregar-poke63 (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 package 'siregar-poke63' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a target for malicious activities.

Vulnerability Detail

The vulnerability in 'siregar-poke63' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall siregar-poke63

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 'siregar-poke63' package and monitor your project for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'siregar-poke63' package poses a significant threat to npm users due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package and monitor your project for vulnerabilities to maintain security.

See every vulnerability recorded for siregar-poke63 →

Share this vulnerability

FAQ

'siregar-poke63' is an npm package associated with a token reward campaign that has been identified as malicious.

The vulnerability can lead to unauthorized changes in your package.json file and may compromise the integrity of your project by introducing malicious code.

You should uninstall the package immediately using 'npm uninstall siregar-poke63' and check your project for any unauthorized changes.

Regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor your project for vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

npm uninstall siregar-poke63

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