Malicious Code Detected in blogpcs Package - Security Alert

blogpcs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15840: Malicious code in blogpcs (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 blogpcs package is an npm library designed for blogging functionalities, allowing developers to integrate various blogging features into their applications. However, it has been identified to contain malicious code, posing a significant security risk to users who implement this package in their projects.

Vulnerability Detail

The vulnerability in the blogpcs package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application. The issue was introduced from version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall blogpcs

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 avoid using the blogpcs package until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The blogpcs package has been identified as containing malicious code, posing serious security risks. Users are advised to remove the package and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for blogpcs →

Share this vulnerability

FAQ

The blogpcs package is an npm library that provides functionalities for integrating blogging features into applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the blogpcs package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

Remove the blogpcs package from your project immediately and consider using a secure alternative package.

How To Fix

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

npm uninstall blogpcs

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