Which versions of @galicia-toolkit-nestjs/swagger are malicious?

The following npm versions of @galicia-toolkit-nestjs/swagger are flagged malicious: 999.0.1, 999.0.2, 999.0.3. Treat any of these as compromised.

How do I remediate @galicia-toolkit-nestjs/swagger if I installed it?

@galicia-toolkit-nestjs/swagger is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @galicia-toolkit-nestjs/swagger — how do I know if it already compromised me?

If @galicia-toolkit-nestjs/swagger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @galicia-toolkit-nestjs/swagger part of a known attack campaign?

Yes — @galicia-toolkit-nestjs/swagger is associated with the IN-MAL-2026-021285, IN-MAL-2026-021301, IN-MAL-2026-021318 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @galicia-toolkit-nestjs/swagger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @galicia-toolkit-nestjs/swagger (3 malicious versions).

Malicious package

@galicia-toolkit-nestjs/swaggernpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

@galicia-toolkit-nestjs/swagger is a confirmed malicious npm package (MAL-2026-17724) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.1, 999.0.2, 999.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @galicia-toolkit-nestjs/swagger (npm)

MAL-2026-17724

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @galicia-toolkit-nestjs/swagger

What this malware does

@galicia-toolkit-nestjs/swagger 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 <hostname>.<tag>.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/<platform>-<arch>/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.

The package presents itself as a NestJS Swagger integration (name resembles @nestjs/swagger, published at version 999.0.2 in a dependency-confusion shape) but ships a stub JavaScript API (forRoot/createLogger returning empty) that, on require(), loads a prebuilt native addon at prebuilds/<platform>-<arch>/metrics.node inside a try/catch that silently swallows errors. The native binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, collects host identity (hostname, uid via getpwuid/getuid, cwd, uname/release, arch, and the package tag passed in via _METRICS_PKG), formats a JSON payload, and sends it over a raw socket (gethostbyname+connect+send, HTTP/1.0 POST /native) to the hardcoded host oob.s4yhii.com. The loader daemonizes via fork+setsid to persist beyond the parent process. On any npm install followed by import/require of this package in a build pipeline, cloud credentials, GitHub Actions OIDC tokens, and npm publish tokens leave the host to an attacker-controlled endpoint.

Malicious versions

3 flagged

999.0.1999.0.2999.0.3

Indicators of compromise (SHA-256)

51d6d85fe98ec0559234e8941f7aa7a2d510233e06277b6c9c576bee6bb65c6b

605d8d8afe172d78840f3617c35733b47635a3482beba461bc1015c45840e250

efeac3bd0d0687def2fa2b9584ca55516aad57a2c94979ef07c26ac48b9f6d20

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @galicia-toolkit-nestjs/swagger (3 malicious versions).
If you installed it — respond
@galicia-toolkit-nestjs/swagger is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @galicia-toolkit-nestjs/swagger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @galicia-toolkit-nestjs/swagger on npm has been identified as a malicious package (versions 999.0.1, 999.0.2, 999.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021285IN-MAL-2026-021301IN-MAL-2026-021318

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @galicia-toolkit-nestjs/swagger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database