Malicious code in @galicia-toolkit-nestjs/paas (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
npm@galicia-toolkit-nestjs/paas
“@galicia-toolkit-nestjs/paas” 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 (4)
- 999.0.3
- 999.0.4
- 999.0.5
- 999.0.6
purl: pkg:npm/%40galicia-toolkit-nestjs/paas
Sources (4)
amazon-inspector
IN-MAL-2026-021324Versions from this source: 999.0.4
sha256: 5c71639b93c4c278d2aed829e538de8512763d09a4fe6336d1a3968b1b1515a0
amazon-inspector
IN-MAL-2026-021334Versions from this source: 999.0.3
sha256: 9ae326eb12d7fa8eb9552bec62a898f2e7c64a4d77c032c02b25b327671ac00e
amazon-inspector
IN-MAL-2026-021303Versions from this source: 999.0.5
sha256: 5df4f7b59cbe90e6b36ce17f0870cd419345167d9aee683d65a43c65ea5fb213
amazon-inspector
IN-MAL-2026-021296Versions from this source: 999.0.6
sha256: 7f03aa4bfecf4a5f4a35eb194aa653bafe31fa35dbfca0dd8367d5d199f25d13
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
@galicia-toolkit-nestjs/paas is a dependency confusion package published to npm on 2026-10-09 by the account s4yhii__, targeting the internal @galicia-toolkit-* / @brick-v2 package namespaces with inflated versions (e.g. 999.0.x). Early versions resolve ..dc.oob.s4yhii.com via DNS to beacon the victim's hostname. Later versions run node index.js from a preinstall hook, which loads a bundled native addon (prebuilds/-/metrics.node, Linux and Windows builds). The addon forks a detached process that collects hostname, username, OS/arch, cwd and the full values of CI/cloud secrets from environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, SYSTEM_ACCESSTOKEN, AZURE_DEVOPS_EXT_PAT and others) and sends them as JSON via HTTP POST /native to oob.s4yhii.com:9999.
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (5df4f7b59cbe90e6b36ce17f0870cd419345167d9aee683d65a43c65ea5fb213)
The package's main entry (index.js) loads a prebuilt native addon (prebuilds/-/metrics.node) inside a try/catch on require. The ELF reads CI and cloud credentials from the environment — AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN — together with host identity and working-directory fields (gethostname, getuid, getpwuid, getcwd, uname) and sends them in a JSON body (fields src, pkg, h, u, os, arch, rel, cwd, e) via a raw socket HTTP POST to oob.s4yhii.com (POST /native HTTP/1.0). The addon imports fork and setsid to daemonize and uses hand-rolled socket/connect/send rather than Node's HTTP API, bypassing Node-level network observability. The package name scope (@galicia-toolkit-nestjs) and implausibly high version (999.0.5) are consistent with a dependency-confusion payload targeting an internal package name. Installing or requiring this package in any environment carrying CI, npm publish, GitHub Actions, or AWS credentials results in those secrets being transmitted to the hardcoded attacker endpoint.