Which versions of @rutxploit-sec/subsplash-canny are malicious?

The following npm versions of @rutxploit-sec/subsplash-canny are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @rutxploit-sec/subsplash-canny if I installed it?

@rutxploit-sec/subsplash-canny establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @rutxploit-sec/subsplash-canny — how do I know if it already compromised me?

If @rutxploit-sec/subsplash-canny 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 @rutxploit-sec/subsplash-canny part of a known attack campaign?

Yes — @rutxploit-sec/subsplash-canny is associated with the IN-MAL-2026-020682 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 @rutxploit-sec/subsplash-canny 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 @rutxploit-sec/subsplash-canny (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rutxploit-sec/subsplash-canny across your stack and pipelines.

Malicious package

@rutxploit-sec/subsplash-cannynpm

@rutxploit-sec/subsplash-canny is a confirmed malicious npm package (MAL-2026-17288) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rutxploit-sec/subsplash-canny (npm)

MAL-2026-17288

Immediate action

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

npm uninstall @rutxploit-sec/subsplash-canny

What this malware does

npm package @rutxploit-sec/subsplash-canny declares a preinstall lifecycle script that runs node -e inline code reading os.hostname() and os.userInfo().username and issuing an HTTP GET to http://127.0.0.1:8099/ with those values as query parameters, plus a package identifier. The package.json description and README self-describe the artifact as a dependency-confusion proof-of-concept impersonating the private scoped name @subsplash/canny. Installing this package on any machine automatically executes the beacon at install time and transmits the installer's hostname and OS username to the configured endpoint. The current destination is loopback (127.0.0.1:8099), which limits real-world reach in this specific tarball, but the mechanism — arbitrary code execution and identity collection on npm install — is fully wired and would function identically against any remote endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

dc1ebadea2eb63a0fc7cf7446e36a589c5b87fc7d28e68b68145b98577107ebb

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @rutxploit-sec/subsplash-canny (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rutxploit-sec/subsplash-canny across your stack and pipelines.
If you installed it — respond
@rutxploit-sec/subsplash-canny establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @rutxploit-sec/subsplash-canny 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 @rutxploit-sec/subsplash-canny 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. @rutxploit-sec/subsplash-canny on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020682

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @rutxploit-sec/subsplash-canny-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database