NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@kite-js-tools/corenpm

Advisory published Updated

@kite-js-tools/core is a confirmed malicious npm package (MAL-2026-12319) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @kite-js-tools/core (npm)

MAL-2026-12319
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @kite-js-tools/core

What this malware does

package.json declares preinstall and postinstall lifecycle scripts that fire automatically on npm install. The preinstall hook performs an HTTPS GET to https://d9hugcagp7gsdcl9dvs0frxfmqc1o8u86.oast.pro/ with the installer's hostname and process PID embedded in the URL path. The postinstall hook performs a DNS resolution against postinstall.<hostname>.d9hugcagp7gsdcl9dvs0frxfmqc1o8u86.oast.pro, leaking the same host identifier via DNS to the same collaborator subdomain. The destination is a Project Discovery Interactsh (OAST) subdomain — out-of-band callback infrastructure typically used to confirm code execution and exfiltrate identifying data from compromised machines. Installer-side host identifiers leave the machine to an attacker-controlled endpoint on every install.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

5fc1e1caf8550f3daa91e586dd7b4eab7f5ec8f62acc12dce63d9d60c293e7c9

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @kite-js-tools/core (version 1.0.0).

  2. If you installed it — respond

    @kite-js-tools/core 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.

  3. Did it already run?

    If @kite-js-tools/core 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. @kite-js-tools/core 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-014874

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @kite-js-tools/core-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
@kite-js-tools/core (npm) malicious package — MAL-2026-12319 | O3 Security