Malicious Code Injection in curious_cephalopod-smiletea Package

curious_cephalopod-smiletea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101145: Malicious code in curious_cephalopod-smiletea (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 curious_cephalopod-smiletea package is part of the npm ecosystem and was associated with a token reward campaign aimed at inflating developer reputation scores. This package is designed to facilitate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that clutter the npm registry, potentially leading to security risks and reputation damage for developers. The package is part of a broader scheme that exploits the npm ecosystem for token rewards, making it a significant threat.

How To Fix

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

npm uninstall curious_cephalopod-smiletea

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 curious_cephalopod-smiletea package and any other packages that may be part of the same token reward scheme. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The curious_cephalopod-smiletea package poses a significant risk due to its malicious code that modifies package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for curious_cephalopod-smiletea →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, potentially causing security risks and affecting the reputation of developers using the package.

You should remove the curious_cephalopod-smiletea package from your project and monitor for any updates or patches.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall curious_cephalopod-smiletea

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