Malicious Code Detected in censorify_jinho82 Package - Security Alert

censorify_jinho82 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16712: Malicious code in censorify_jinho82 (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 censorify_jinho82 package is an npm module designed to provide content censorship functionalities in JavaScript applications. It allows developers to filter or block specific content based on predefined rules. However, this package has been identified to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the censorify_jinho82 package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this package. This code could potentially allow unauthorized access to sensitive data, execute arbitrary commands, or disrupt application functionality. The malicious nature of this code was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall censorify_jinho82

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 an immediate workaround, you can replace the censorify_jinho82 package with an alternative content censorship library that has been vetted for security. Ensure to review the documentation of the alternative package to integrate it properly into your application.

Conclusion

The censorify_jinho82 package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is crucial to remove this package and consider alternatives to ensure the security of your application. Regularly monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for censorify_jinho82 →

Share this vulnerability

FAQ

censorify_jinho82 is an npm package used for content censorship in JavaScript applications, allowing developers to filter or block specific content.

The malicious code found in censorify_jinho82 can compromise application security, potentially allowing unauthorized access and execution of harmful commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

The best mitigation strategy is to remove the censorify_jinho82 package and replace it with a secure alternative. There are no safe workarounds for using this compromised package.

The vulnerability was discovered by Amazon Inspector, a security tool that identifies potential security risks in applications.

How To Fix

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

npm uninstall censorify_jinho82

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