Malicious Code Vulnerability in like_shark-appteadev Package

like_shark-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105139: Malicious code in like_shark-appteadev (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 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 like_shark-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. This package has been identified as part of a broader malicious campaign that exploits npm's package management system. It is designed to manipulate package metadata and publish derivative packages, which can lead to reputation inflation for malicious actors.

Vulnerability Detail

The vulnerability originates from the like_shark-appteadev package being involved in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall like_shark-appteadev

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 like_shark-appteadev package and replace it with a trusted alternative. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The like_shark-appteadev package poses a significant risk due to its involvement in a malicious campaign that manipulates npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for like_shark-appteadev →

Share this vulnerability

FAQ

The like_shark-appteadev package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, making it challenging to find legitimate packages and potentially exposing your application to further security risks.

If you have installed the like_shark-appteadev package, you should uninstall it immediately using 'npm uninstall like_shark-appteadev' and review your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

There is no patch for the like_shark-appteadev package since it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall like_shark-appteadev

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