{"answers":{"affected":"1 open source package ship an affected version, including publish-poc-test3.","exploited":"There is no known exploitation of MAL-2026-18324 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-18324 is a malicious package in publish-poc-test3, published on 26 Oct 2026."},"fix_prompt":"MAL-2026-18324 is a malicious package: publish-poc-test3 (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-18324/ (Markdown: https://insights.sbomify.com/MAL-2026-18324/index.md)","id":"MAL-2026-18324","markdown":"https://insights.sbomify.com/MAL-2026-18324/index.md","name":"MAL-2026-18324","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The package's postinstall lifecycle script creates a temporary directory, writes a fabricated package.json whose name is 'publish-poc-found-\u003crandom-hex\u003e' (random suffix derived via 'openssl rand -hex 2'), and then invokes 'npm publish' from that directory. The literal string 'npm publish' is reconstructed at runtime by concatenating three fragments ('np', 'm pu', 'blish') through printf, specifically to prevent manifest and string scanners from matching the command. The publish runs against the public npm registry using whatever npm authentication context the installing environment currently has (an _authToken from ~/.npmrc, NPM_TOKEN / NODE_AUTH_TOKEN in the environment, or an active CI publish identity), so running 'npm install' of this package on a developer workstation or CI host that holds publish rights causes a new attacker-named package to be published under the installer's npm identity. The combination of credential abuse at install time, randomized attacker-chosen package naming, and deliberate obfuscation of the exact command performing the publish is characteristic registry self-propagation / worm behavior.","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 publish-poc-test3 (npm)","id":"MAL-2026-18324","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":"publish-poc-test3","purl":"pkg:npm/publish-poc-test3","source":"MAL-2026-18324"}],"products":null,"published":"2026-10-26","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-18324/"}