Critical Malware Threat in serpacksven Package: Embedded Malicious Code Detected

serpacksven Updated 06 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17625: Malicious code in serpacksven (npm). Affects serpacksven versions 1.0.0 – 1.0.4. 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 serpacksven package is an npm library that is intended for JavaScript functionality. However, it has been found to contain malicious code that compromises the security of systems using it. This package lacks a functional main entry point, rendering it non-operational as a legitimate library, and instead includes an obfuscated PowerShell script that poses significant security risks.

Vulnerability Detail

The vulnerability originates from the inclusion of a heavily obfuscated PowerShell script within the package. This script hides its execution from the user, performs various anti-analysis techniques, and ultimately loads a .NET assembly that is controlled by an attacker. The presence of this malicious code means that any system running this package is at risk of being fully compromised, with potential exposure of sensitive information and unauthorized access to the system.

How To Fix

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

npm uninstall serpacksven

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 executing any scripts or commands that may invoke the json.txt file included in the package. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The discovery of malicious code within the serpacksven package highlights the importance of vigilance when using open-source libraries. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for serpacksven →

Share this vulnerability

FAQ

serpacksven is an npm package intended for JavaScript functionality, but it has been identified as containing malicious code.

The malicious code is an obfuscated PowerShell script that hides its execution and loads a .NET assembly controlled by an attacker.

You should immediately remove the serpacksven package from your project and rotate any sensitive information stored on the affected system.

While many npm packages are safe, it is crucial to monitor for vulnerabilities and verify the integrity of packages before installation.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities by analyzing your package-lock.json file.

How To Fix

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

npm uninstall serpacksven

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