Malicious code in testepoc20232 (npm)

testepoc20232 Updated 02 Oct 2025

Summary

03/12/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8657: Malicious code in testepoc20232 (npm). Affects testepoc20232 versions 1.0.0. 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 package 'testepoc20232' is an npm package that is used for testing purposes. It is designed to provide a testing environment for developers. However, this specific version, 1.0.0, has been identified as malicious by the OpenSSF Package Analysis project. The package has been found to communicate with a domain associated with malicious activity.

Vulnerability Detail

The vulnerability in 'testepoc20232' version 1.0.0 lies in its communication with a domain linked to malicious activity. This behavior raises concerns about the package's intentions and potential impact on the system. The malicious code within the package could potentially compromise the security of the system, leading to unauthorized access, data breaches, or other malicious activities.

How To Fix

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

npm uninstall testepoc20232

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

There is no specific workaround mentioned for this vulnerability. The best course of action is to remove the 'testepoc20232' package as described in the 'how_to_fix' section.

Conclusion

The 'testepoc20232' package version 1.0.0 has been identified as malicious due to its communication with a domain associated with malicious activity. It is recommended to remove this package from your project and take appropriate security measures to ensure the integrity of your system. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for testepoc20232 →

Share this vulnerability

FAQ

This vulnerability could potentially compromise the security of the system, leading to unauthorized access, data breaches, or other malicious activities.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply enter your package-lock.json file and the playground will analyze it for any open-source vulnerabilities, including this one.

Yes, the recommended fix is to remove the 'testepoc20232' package from your project and update your dependencies.

It is advisable to avoid using any version of 'testepoc20232' until the issue has been resolved and a secure version is available.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in resolving this vulnerability.

How To Fix

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

npm uninstall testepoc20232

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