Malicious Code Detected in 'test-on-other-again' Package - Version 99.9.8

test-on-other-again Updated 23 Jan 2026

Summary

23/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-491: Malicious code in test-on-other-again (npm). Affects test-on-other-again versions 99.9.8. 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 'test-on-other-again' package is an npm module designed for testing purposes within JavaScript applications. It allows developers to run tests in various environments. However, the package has been flagged for malicious behavior, raising concerns about its integrity and security.

Vulnerability Detail

The vulnerability in the 'test-on-other-again' package arises from its communication with a domain linked to malicious activities. Additionally, it executes commands that are associated with harmful behavior, potentially compromising the security of applications that utilize this package. This can lead to unauthorized access, data breaches, or further exploitation of the system.

How To Fix

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

npm uninstall test-on-other-again

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, you can avoid using the 'test-on-other-again' package altogether. Instead, consider using alternative testing frameworks such as Jest or Mocha, which are widely recognized and have a strong community backing.

Conclusion

The 'test-on-other-again' package has been identified as malicious due to its harmful behavior and communication with malicious domains. It is crucial for developers to take immediate action by removing the package and considering secure alternatives to protect their applications.

See every vulnerability recorded for test-on-other-again →

Share this vulnerability

FAQ

It is an npm module used for testing JavaScript applications, allowing developers to run tests in different environments.

The package communicates with a domain associated with malicious activities and executes harmful commands.

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

Remove the affected version and replace it with a secure alternative or update to the latest patched version if available.

Yes, consider using testing frameworks like Jest or Mocha, which are reputable and widely used in the JavaScript community.

How To Fix

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

npm uninstall test-on-other-again

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