Malicious Code Detected in abartelsmeier-test Package

abartelsmeier-test Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13945: Malicious code in abartelsmeier-test (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The abartelsmeier-test package is an npm module designed for testing purposes. It is utilized by developers to facilitate various testing scenarios in JavaScript applications. However, this package has been found to contain malicious code, posing a significant risk to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the abartelsmeier-test package. This code can potentially compromise the security of applications that use this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in 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 abartelsmeier-test

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 workaround, users can temporarily avoid using the abartelsmeier-test package and explore alternative packages that provide similar functionality without the associated risks.

Conclusion

The abartelsmeier-test package has been identified as containing malicious code, posing a risk to users. It is crucial to remove this package from any projects and monitor for updates or alternatives to ensure application security.

See every vulnerability recorded for abartelsmeier-test →

Share this vulnerability

FAQ

The abartelsmeier-test package is an npm module used for testing purposes in JavaScript applications.

The vulnerability is due to the presence of malicious code that can compromise the security of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

It is recommended to remove the package from your project and replace it with a secure alternative.

Currently, there is no patched version available for the abartelsmeier-test package.

How To Fix

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

npm uninstall abartelsmeier-test

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