Malicious Code Injection in siregar-poke33: A Threat to npm Ecosystem

siregar-poke33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165951: Malicious code in siregar-poke33 (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

siregar-poke33 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The functionality of siregar-poke33 is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in siregar-poke33 stems from its inclusion in a broader malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers and users relying on legitimate packages.

How To Fix

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

npm uninstall siregar-poke33

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, avoid using the siregar-poke33 package and monitor your project for any dependencies that may have been affected by this malicious code. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the siregar-poke33 package highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking proactive steps to remove affected packages, developers can safeguard their projects from potential threats.

See every vulnerability recorded for siregar-poke33 →

Share this vulnerability

FAQ

siregar-poke33 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially causing conflicts with legitimate packages and compromising the integrity of your project.

You should uninstall the siregar-poke33 package immediately using the command 'npm uninstall siregar-poke33' and check for any other affected dependencies.

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

There is no patch available for siregar-poke33 as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall siregar-poke33

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