Which versions of strapi-plugin-nordica are malicious?

The following npm versions of strapi-plugin-nordica are flagged malicious: 1.0.0, 3.6.10. Treat any of these as compromised.

How do I remediate strapi-plugin-nordica if I installed it?

strapi-plugin-nordica 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 strapi-plugin-nordica — how do I know if it already compromised me?

If strapi-plugin-nordica was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is strapi-plugin-nordica part of a known attack campaign?

Yes — strapi-plugin-nordica is associated with the GHSA-vq87-37pj-9m5x 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 strapi-plugin-nordica across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-nordica (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-nordica across your stack and pipelines.

Malicious package

strapi-plugin-nordicanpm

Malicious code in strapi-plugin-nordica (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2471

Immediate action

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

npm uninstall strapi-plugin-nordica

What this malware does

strapi-plugin-nordica is a malicious npm package disguised as a Strapi CMS plugin. On install, it runs a postinstall script that executes an 11-phase attack: stealing .env files, environment variables, Strapi configuration, private keys, Redis data, Docker/Kubernetes secrets, and network topology. It then opens a polling C2 loop that accepts and executes arbitrary shell commands from a remote server.

The package strapi-plugin-nordica was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.03.6.10

Indicators of compromise (SHA-256)

60884da6df873a8ce1cfa8ce8662f03927387d243b32069ca73fe2536b8bfe7e

9a29a609e4151fce2c50e6011bba0003b4f0bcc69729d304df0d40438e0911ef

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for strapi-plugin-nordica (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging strapi-plugin-nordica across your stack and pipelines.
If you installed it — respond
strapi-plugin-nordica 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 strapi-plugin-nordica was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks strapi-plugin-nordica before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. strapi-plugin-nordica on npm has been identified as a malicious package (versions 1.0.0, 3.6.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vq87-37pj-9m5x

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks strapi-plugin-nordica-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