Critical Vulnerability in @lain-test-org/test-package2: Embedded Malicious Code Detected

@lain-test-org/test-package2 Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6141: Malicious code in @lain-test-org/test-package2 (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 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

The package @lain-test-org/test-package2 is a Node.js library designed for various functionalities within JavaScript applications. It is part of the npm ecosystem, which is widely used for package management in JavaScript. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, potentially leading to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @lain-test-org/test-package2 package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. The ramifications include the potential theft of sensitive information, such as secrets and keys, which could lead to further exploitation. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall @lain-test-org/test-package2

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, it is recommended to rotate all secrets and keys stored on the compromised system from a different, secure computer. This action is crucial to mitigate any potential damage caused by the malicious code.

Conclusion

The @lain-test-org/test-package2 package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @lain-test-org/test-package2 →

Share this vulnerability

FAQ

Immediately remove the package from your system and rotate any sensitive information stored on that computer.

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

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

Rotating secrets and keys is crucial to prevent unauthorized access to your systems and data, especially after a compromise.

How To Fix

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

npm uninstall @lain-test-org/test-package2

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