Malicious code in @tqm-mfe/main (npm)
The npm package @tqm-mfe/main version 5.4.7 contains malicious code in its postinstall.js lifecycle script. This script is heavily obfuscated and executes automatically on npm install. It performs environment checks to evade sandbox detection, downloads a remote binary payload, decrypts it, writes it to a persistent app-data directory, marks it executable, and runs it detached from the installer process. Additionally, it sends system information to a remote server. The package metadata is deceptive, mimicking an internal corporate mirror but is actually a dependency-confusion lure. This behavior is unrelated to the package's advertised functionality.
AI Analysis
Technical Summary
The @tqm-mfe/main npm package at version 5.4.7 includes a malicious postinstall.js script that uses advanced obfuscation techniques to evade detection. Upon installation, it verifies the environment to avoid sandbox analysis, fetches a remote encrypted binary, decrypts and installs it persistently on the system, and executes it in a detached manner to maintain persistence beyond the npm process. Concurrently, it exfiltrates system metadata to a remote server. The package's public metadata falsely represents it as an internal corporate tool, consistent with a dependency confusion attack vector targeting organizations that might resolve the @tqm-mfe scope from the public npm registry. None of these actions are required for the purported API mocking middleware functionality.
Potential Impact
This malicious package can lead to unauthorized code execution on the affected system, persistent installation of unknown binaries, and exfiltration of system information to an attacker-controlled server. This compromises system integrity and confidentiality. The obfuscation and sandbox evasion techniques increase the difficulty of detection and analysis.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. The best mitigation is to avoid installing version 5.4.7 of @tqm-mfe/main from public npm registries. Organizations should audit their dependencies for this package and remove it if found. Use strict package source controls and consider implementing dependency allowlists or private registries to prevent dependency confusion attacks. Monitor for unexpected postinstall scripts in npm packages.
Malicious code in @tqm-mfe/main (npm)
Description
The npm package @tqm-mfe/main version 5.4.7 contains malicious code in its postinstall.js lifecycle script. This script is heavily obfuscated and executes automatically on npm install. It performs environment checks to evade sandbox detection, downloads a remote binary payload, decrypts it, writes it to a persistent app-data directory, marks it executable, and runs it detached from the installer process. Additionally, it sends system information to a remote server. The package metadata is deceptive, mimicking an internal corporate mirror but is actually a dependency-confusion lure. This behavior is unrelated to the package's advertised functionality.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @tqm-mfe/main npm package at version 5.4.7 includes a malicious postinstall.js script that uses advanced obfuscation techniques to evade detection. Upon installation, it verifies the environment to avoid sandbox analysis, fetches a remote encrypted binary, decrypts and installs it persistently on the system, and executes it in a detached manner to maintain persistence beyond the npm process. Concurrently, it exfiltrates system metadata to a remote server. The package's public metadata falsely represents it as an internal corporate tool, consistent with a dependency confusion attack vector targeting organizations that might resolve the @tqm-mfe scope from the public npm registry. None of these actions are required for the purported API mocking middleware functionality.
Potential Impact
This malicious package can lead to unauthorized code execution on the affected system, persistent installation of unknown binaries, and exfiltration of system information to an attacker-controlled server. This compromises system integrity and confidentiality. The obfuscation and sandbox evasion techniques increase the difficulty of detection and analysis.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package. The best mitigation is to avoid installing version 5.4.7 of @tqm-mfe/main from public npm registries. Organizations should audit their dependencies for this package and remove it if found. Use strict package source controls and consider implementing dependency allowlists or private registries to prevent dependency confusion attacks. Monitor for unexpected postinstall scripts in npm packages.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10517
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff7d68715ace432f387e
Added to database: 07/14/2026, 09:21:01 UTC
Last enriched: 07/14/2026, 09:39:56 UTC
Last updated: 07/25/2026, 11:18:15 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.