Malicious Code Injection in oytrii-devapp: A Threat to npm Packages

oytrii-devapp Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106876: Malicious code in oytrii-devapp (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 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

oytrii-devapp is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the ecosystem, but it has been compromised to include malicious code. The vulnerability stems from the package's ability to modify its own metadata, which can lead to severe consequences for developers and users relying on its integrity.

Vulnerability Detail

The vulnerability in oytrii-devapp originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of reputation damage for developers and potential security threats for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall oytrii-devapp

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 oytrii-devapp package until a patched version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The oytrii-devapp package has been compromised with malicious code that alters its metadata and floods the npm registry. Developers and users should take immediate action to update or avoid this package to mitigate potential risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for oytrii-devapp →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and floods the npm registry with compromised packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

The consequences include reputation damage for developers, security risks for users, and pollution of the npm registry with malicious packages.

Yes, you can avoid using the oytrii-devapp package and run npm audit to identify other vulnerabilities in your dependencies.

The vulnerability was reported by Amazon Inspector, a tool designed to identify security issues in software packages.

How To Fix

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

npm uninstall oytrii-devapp

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