Which versions of goofy-sdk are malicious?

The following npm versions of goofy-sdk are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate goofy-sdk if I installed it?

goofy-sdk 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 goofy-sdk — how do I know if it already compromised me?

If goofy-sdk 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 goofy-sdk part of a known attack campaign?

Yes — goofy-sdk is associated with the IN-MAL-2026-008121 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 goofy-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for goofy-sdk (version 9999.0.0).

Malicious package

goofy-sdknpm

Advisory published Jul 8, 2026Updated Jul 8, 2026

goofy-sdk is a confirmed malicious npm package (MAL-2026-6997) that opens a backdoor for remote access (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in goofy-sdk (npm)

MAL-2026-6997

Immediate action

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

npm uninstall goofy-sdk

What this malware does

[email protected] is a dependency-confusion squat: the version is inflated to 9999.0.0 to shadow an internal package of the same name in build systems that resolve unscoped names against the public npm registry. On install, the package's preinstall hook executes callback.js, which reads os.hostname(), os.userInfo().username, process.platform, and process.cwd() and transmits them out-of-band to *.oast.fun (Interactsh OAST callback infrastructure) via a DNS subdomain-encoded lookup and an HTTPS POST. Any build system that mis-resolves the internal name to this public package will silently leak internal host identity to a third-party callback service. Self-declared bug-bounty/research framing does not change the installer-side impact — the harm (unconsented host-identity beacon on install) is the same regardless of motive.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

779daa3389f4ff3ea7ca2acb4e0202b4465e90fa0d8b7bdcc0e3785f34e454a2

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for goofy-sdk (version 9999.0.0).
If you installed it — respond
goofy-sdk 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 goofy-sdk 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. goofy-sdk on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008121

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks goofy-sdk-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