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

The following npm versions of @galicia-toolkit-nestjs-20/commons 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-20/commons if I installed it?

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

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

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

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

Malicious package

@galicia-toolkit-nestjs-20/commonsnpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

@galicia-toolkit-nestjs-20/commons is a confirmed malicious npm package (MAL-2026-17726) 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-20/commons (npm)

MAL-2026-17726

Immediate action

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

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

What this malware does

@galicia-toolkit-nestjs-20/commons 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 require(), index.js loads a bundled ELF native addon at prebuilds/linux-x64/metrics.node inside a silent try/catch. The addon reads CI/cloud credential environment variables (AWS_SECRET_ACCESS_KEY and related AWS_*, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, ACTIONS_RUNTIME_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN) along with hostname, user, and cwd, and POSTs them as JSON to the hardcoded non-first-party host oob.s4yhii.com at the path /native. The addon also calls fork and setsid to detach from the loader process after transmission, so the exfiltration continues in the background without blocking the caller. The package ships at version 999.0.1 under scope @galicia-toolkit-nestjs-20 with no library functionality beyond loading this addon — the inflated version, scope-mimicry, and payload-only contents are the canonical dependency-confusion shape. Packaging the exfiltration logic as a compiled.node binary rather than JavaScript, combined with the silent try/catch loader and the fork+setsid detach, is deliberate anti-analysis around the credential-theft primitive.

Malicious versions

3 flagged

999.0.1999.0.2999.0.3

Indicators of compromise (SHA-256)

418f9501530a35aa52b2c35b7ce12d757c8472763708baa60097f3e1a6d8d4e5

46e8c8fd81b9076dcfdfd0296e023046283d466f75c04e28bfd55e8ef1a6ea52

5b719740efc4b3e93e85668e2e787b39a8d91e15abbe9c39f5d156e118745caa

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @galicia-toolkit-nestjs-20/commons (3 malicious versions).
If you installed it — respond
@galicia-toolkit-nestjs-20/commons 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/commons 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/commons 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-021306IN-MAL-2026-021287IN-MAL-2026-021319

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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