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

siregar-poke48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165967: Malicious code in siregar-poke48 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The siregar-poke48 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These malicious packages are designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in siregar-poke48 stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is orchestrated by autopublish scripts that continuously republish variants of the package, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly incorporate these malicious packages into their projects, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall siregar-poke48

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-poke48 package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any signs of malicious activity.

Conclusion

The siregar-poke48 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and take immediate action to remove this package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for siregar-poke48 →

Share this vulnerability

FAQ

Siregar-poke48 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and integrity.

You should uninstall the package immediately using the command npm uninstall siregar-poke48.

Regularly monitor your dependencies for vulnerabilities and use tools like Vulert to check for open-source vulnerabilities in your software.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.

How To Fix

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

npm uninstall siregar-poke48

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