registry / Destructive action / mcc-compiler
mcc-compiler
Majo C Compiler - 一个有教养的编译器，必须说 --please 才会编译
This report shows the evidence for mcc-compiler@1.0.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package performs a concrete, destructive system-wide executable replacement during postinstall. Its transparency reduces deception risk but does not remove the harmful install-time attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install executes postinstall with permission to write /usr/bin.
Impact
Disrupts or controls subsequent system-wide gcc invocations; original compiler may be left unavailable if restoration fails.
Mechanism
system compiler replacement via rename, unlink, and symlink
Attack narrative
On install, the lifecycle hook tests write access to /usr/bin, renames the existing gcc binary to gcc.real, then removes any remaining gcc path and symlinks it to mcc. Later gcc invocations run the wrapper, which exits with an error unless its custom flow is used. Although the behavior is documented and has an uninstall restoration attempt, it is an unconsented install-time system-wide compiler hijack.
AI rationale
The package performs a concrete, destructive system-wide executable replacement during postinstall. Its transparency reduces deception risk but does not remove the harmful install-time attack surface.
Evidence
package.jsonscripts/postinstall.jsscripts/preuninstall.jssrc/index.js/usr/bin/.mcc_test/usr/bin/gcc/usr/bin/gcc.real
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- postinstall runs automatically during installation.
- Installer renames /usr/bin/gcc to /usr/bin/gcc.real.
- Installer deletes and replaces /usr/bin/gcc with an mcc symlink.
- Runtime wrapper intentionally makes gcc invocations fail without its custom flag.
Evidence against
- No network, credential collection, payload download, or dynamic-code execution found.
- The package documents the compiler replacement and provides an uninstall restoration path.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
2 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
1 High3 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to mcc-compiler@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing mcc-compiler@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.