Credential Stealer in data-pipeline-testmetest: A Malicious npm Package

data-pipeline-testmetest Updated 22 Oct 2026

Summary

21/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18177: Malicious code in data-pipeline-testmetest (npm). Affects data-pipeline-testmetest versions 2.0.1. 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

data-pipeline-testmetest is an npm package designed for testing data pipelines. It is intended to provide utilities for developers working with data processing. However, version 2.0.1 of this package has been identified as malicious, containing code that executes harmful actions upon installation, compromising user credentials and system integrity.

Vulnerability Detail

The vulnerability arises from the package's use of a binding.gyp file that executes an obfuscated loader during the installation process. This loader decrypts a large payload that steals sensitive credentials from various platforms, including GitHub and npm, and commits them to a public repository created in the victim's GitHub account. The malicious code also installs a service that can delete user files if a stolen GitHub token is revoked, posing significant risks to users' data and security.

How To Fix

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

npm uninstall data-pipeline-testmetest

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 workaround, users can remove the malicious script by deleting the following files before revoking any GitHub tokens: rm -rf ~/.local/bin/net-health-checker.sh and its associated systemd unit or LaunchAgent.

Conclusion

The data-pipeline-testmetest package version 2.0.1 contains a severe vulnerability that can compromise user credentials and system integrity. Immediate action is required to mitigate risks, including uninstalling the package and monitoring for any unauthorized access.

See every vulnerability recorded for data-pipeline-testmetest →

Share this vulnerability

FAQ

It is intended to provide utilities for testing data pipelines in software development.

The vulnerability executes malicious code during installation, which steals credentials and can delete user files.

Uninstall the package immediately and check for any unauthorized access to your accounts.

Yes, tools like Vulert can monitor your package-lock.json for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.

How To Fix

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

npm uninstall data-pipeline-testmetest

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