Malicious Code Detected in 'othw' Package - Version 999.0.0

othw Updated 20 Dec 2025

Summary

20/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192681: Malicious code in othw (npm). Affects othw versions 999.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 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 'othw' package is a Node.js library available through npm, designed to facilitate various functionalities in JavaScript applications. However, it has been flagged for malicious behavior, specifically for communicating with domains associated with harmful activities. This vulnerability poses a significant risk to applications relying on this package, as it may lead to data breaches or unauthorized access.

Vulnerability Detail

The vulnerability in the 'othw' package arises from its version 999.0.0, which has been identified as malicious by the OpenSSF Package Analysis project. The package's communication with a domain linked to malicious activities raises concerns about potential data exfiltration and security breaches. Users of this package are at risk of having their applications compromised, leading to severe ramifications such as loss of sensitive data and unauthorized access to systems.

How To Fix

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

npm uninstall othw

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 remove the 'othw' package from your project by executing the command: npm uninstall othw. This will prevent any malicious code from executing while you search for a suitable alternative.

Conclusion

The 'othw' package version 999.0.0 has been identified as malicious, posing significant risks to applications that utilize it. Users are advised to uninstall the package and seek alternatives to ensure the security of their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application integrity.

See every vulnerability recorded for othw →

Share this vulnerability

FAQ

The 'othw' package is a Node.js library available on npm, used for various functionalities in JavaScript applications.

'othw' version 999.0.0 is flagged as malicious due to its communication with a domain associated with harmful activities.

Using the 'othw' package can lead to data breaches, unauthorized access, and potential compromise of your application.

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

If you have used the 'othw' package, it is crucial to uninstall it immediately and look for a secure alternative to mitigate any potential risks.

How To Fix

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

npm uninstall othw

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