supply chain event / NVI-00010873 / Revision 1
Malicious code in cortana-md-engine (npm)
GitHub lists this malware advisory for cortana-md-engine. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
cortana-md-engine
source listed= 1.4.6
## Source: amazon-inspector (9a2de4b6992a1dd7177803253b8c214d1ba7cc911cf0e1e7f800e1e9ff7ab5b1) cortana-md-engine is a Baileys-based WhatsApp bot whose bundled entrypoints dist/hosted.cjs and dist/index.cjs hardcode five mongodb+srv://cortanauser:...@{cluster2.uvds2qk,cluster3.t2gtazm,cluster4.bwuctn9,cluster5.kdkad04,mass.gcijtck}.mongodb.net Atlas connection strings and, at bot startup, persist the Baileys authState/creds (Session/authState/sessions collections) into those clusters. The MongoDB user credentials are baked into the shipped JavaScript, so the author retains read access to every installer's linked WhatsApp session state — sufficient to hijack the linked WhatsApp account. The relay is not disclosed in the README, which only instructs the user to run npm start. The tarball additionally ships offensive tooling aimed at third-party WhatsApp users (a ~150-entry proxy pool in dist/proxies.cjs, batched reaction and socket-spoof flooding in dist/react-engine.cjs, and abuse commands such as perm-ban-num, cortana-ios-crash, realban, massreport); this is operator-directed abuse capability, separate from the installer-side session exfiltration. --- Credit: [OpenSSF](https://git
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-25rm-w924-v83v ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.