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

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

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

@galicia-toolkit-nestjs-20/archetype 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-20/archetype — how do I know if it already compromised me?

If @galicia-toolkit-nestjs-20/archetype 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-20/archetype part of a known attack campaign?

Yes — @galicia-toolkit-nestjs-20/archetype is associated with the IN-MAL-2026-021307, IN-MAL-2026-021323 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-20/archetype across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @galicia-toolkit-nestjs-20/archetype (2 malicious versions).

Malicious package

@galicia-toolkit-nestjs-20/archetypenpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

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

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

MAL-2026-17725

Immediate action

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

npm uninstall @galicia-toolkit-nestjs-20/archetype

What this malware does

@galicia-toolkit-nestjs-20/archetype 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.

On module load, index.js unconditionally require()s a bundled native binary at prebuilds/<platform>-<arch>/metrics.node inside a try/catch that swallows errors. The ELF reads installer-side credential-grade environment variables (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) along with hostname, uid, cwd, and uname, and POSTs a JSON payload to the hardcoded host oob.s4yhii.com via a raw 'POST /native HTTP/1.0' request. The binary calls fork+setsid to detach from the host process. The exfiltration destination is embedded inside the compiled addon rather than exposed in JavaScript, placing it beyond source-level inspection. The declared package scope (NestJS archetype toolkit) has no relationship to the destination host or to native-code execution, and the package ships no C/C++ sources corresponding to the shipped.node binary.

Malicious versions

2 flagged

999.0.1999.0.2

Indicators of compromise (SHA-256)

662603823964bdbc871f386498e949d768c84d99645690ee3b5e904b458536db

b494c2f9dc32618d0dc946ba4570f3fe98475a4f32d29a3996ae0a2f8b2271ac

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @galicia-toolkit-nestjs-20/archetype (2 malicious versions).
If you installed it — respond
@galicia-toolkit-nestjs-20/archetype 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-20/archetype 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-20/archetype on npm has been identified as a malicious package (versions 999.0.1, 999.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021307IN-MAL-2026-021323

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @galicia-toolkit-nestjs-20/archetype-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