Malicious Code Injection in instant_silkworm-silentdev Package

instant_silkworm-silentdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104251: Malicious code in instant_silkworm-silentdev (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 instant_silkworm-silentdev package is part of the npm ecosystem, primarily used for JavaScript development. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a scheme that generates and publishes derivative packages with the intent to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the instant_silkworm-silentdev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and the degradation of the npm ecosystem through the proliferation of malicious packages.

How To Fix

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

npm uninstall instant_silkworm-silentdev

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 instant_silkworm-silentdev package from your project by executing: npm uninstall instant_silkworm-silentdev. This will prevent the execution of the malicious code until a fix is applied.

Conclusion

The instant_silkworm-silentdev package contains a significant vulnerability that can compromise the integrity of your project. It is crucial to take immediate action by updating or removing the package and monitoring your dependencies for any future vulnerabilities.

See every vulnerability recorded for instant_silkworm-silentdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the generation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive information and degrading the integrity of your project.

You should immediately uninstall the package and update your project dependencies to remove any traces of the malicious code.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

Regularly update your dependencies, monitor your packages for vulnerabilities using tools like Vulert, and review your package.json for any unauthorized changes.

How To Fix

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

npm uninstall instant_silkworm-silentdev

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