Malicious code in publish-poc-test3 (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
npmpublish-poc-test3
“publish-poc-test3” 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 (7)
- 1.0.15
- 1.0.18
- 1.0.19
- 1.0.21
- 1.0.22
- 1.0.26
- 1.0.27
purl: pkg:npm/publish-poc-test3
Sources (7)
amazon-inspector
IN-MAL-2026-021779Versions from this source: 1.0.15
sha256: 0e68efd8003626562d8bdc2d5d3df97b9f4d876a63571038d8ac813da516851c
amazon-inspector
IN-MAL-2026-021776Versions from this source: 1.0.27
sha256: 17ed061cc2981149c8777982d072a5209edb74a870af8f8af2b524d7f7f1a185
amazon-inspector
IN-MAL-2026-021772Versions from this source: 1.0.18
sha256: 4001a75b24abfa181a10e5d40931194f254304fcf5fda554488d3c242cc5db85
amazon-inspector
IN-MAL-2026-021777Versions from this source: 1.0.22
sha256: 8ac06791d61a7ac29d00c3febfba325c7e2fe98b8dc4804d522644695f1a8466
amazon-inspector
IN-MAL-2026-021783Versions from this source: 1.0.19
sha256: adb3a005f2e2780f849662a8314ad7fc57ed7fb9f2648b71a3857a5de9c4debf
amazon-inspector
IN-MAL-2026-021778Versions from this source: 1.0.26
sha256: b5368db720474af1decca74b6232508e5c180df80abb4c6a4c2a3e5f4b459e21
amazon-inspector
IN-MAL-2026-021773Versions from this source: 1.0.21
sha256: bbce58a5e855198cf4d8c8e1b0ec5175fb83cc1054dd28aa26bab3566a334f79
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
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (4001a75b24abfa181a10e5d40931194f254304fcf5fda554488d3c242cc5db85)
The package's postinstall lifecycle script creates a temporary directory, writes a fabricated package.json whose name is 'publish-poc-found-' (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.