Which versions of @goparrot-dashboard/category are malicious?

The following npm versions of @goparrot-dashboard/category are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @goparrot-dashboard/category if I installed it?

Remove @goparrot-dashboard/category from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @goparrot-dashboard/category — how do I know if it already compromised me?

If @goparrot-dashboard/category 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.

How do I find @goparrot-dashboard/category across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @goparrot-dashboard/category (version 0.0.1).

Part of a larger attack: @goparrot-dashboard published 20 malicious packages. See the full campaign →

Malicious package

@goparrot-dashboard/categorynpm

Advisory published Nov 2, 2026Updated Nov 3, 2026

@goparrot-dashboard/category is a confirmed malicious npm package (MAL-2026-18495) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @goparrot-dashboard/category (npm)

MAL-2026-18495

Immediate action

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

npm uninstall @goparrot-dashboard/category

What this malware does

@goparrot-dashboard/category is a dependency-confusion probe: it takes a name in a @goparrot-dashboard scope that its publisher created on npm, next to GoParrot's public @goparrot scope, so a build that resolves that scope from npm gets it instead of a private package of the same name. Version 0.0.1 has no install scripts, and its index.js only prints a "[rootxravi-poc-security] @goparrot-dashboard/category" marker when loaded. The npm account devtest91001 published it on 2026-11-01 with 24 other packages in @goparrot-dashboard and @goparrot-dashboard-api, including @goparrot-dashboard/app, whose 0.0.2 sends the hostname, user and working directory to an interactsh callback host (iuczektmwpudhwqnsbkgc6m8nx2dgn5vc.oast.fun) from a preinstall script.

Malicious versions

1 flagged

0.0.1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @goparrot-dashboard/category (version 0.0.1).
If you installed it — respond
Remove @goparrot-dashboard/category from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @goparrot-dashboard/category 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. @goparrot-dashboard/category on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

npmjs.com

Credits

InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @goparrot-dashboard/category-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database