cutekitten-test@1.0.1
Security test package for a school project: its preinstall hook posts the installing machine's hostname and username to a Discord webhook to demonstrate npm lifecycle risks. Do not install unless you are testing this.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest enables an install-time hook that sends the machine hostname and OS username to a hardcoded Discord webhook. The README discloses the behavior, but it runs automatically without installer consent, meeting the install-time data exfiltration rule.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Automatic npm preinstall lifecycle hook.
Impact
Discloses the installing machine's hostname and username to the webhook receiver.
Mechanism
Reads the hostname and OS username and includes them in a POST to the embedded webhook URL; writes a local marker with the result.
Attack narrative
During npm installation, the preinstall hook obtains the machine hostname and OS username and POSTs them to a hardcoded Discord webhook. It also writes a local marker with the event and request result. The README discloses this demonstration behavior, but the transfer is still automatic and lacks installer consent.
AI rationale
The manifest enables an install-time hook that sends the machine hostname and OS username to a hardcoded Discord webhook. The README discloses the behavior, but it runs automatically without installer consent, meeting the install-time data exfiltration rule.
Evidence
package.jsonpreinstall.jsREADME.md.preinstall-marker.json
Network endpoints1
canary.discord.com/api/webhooks/1566232728179843243/pM5rDIrCRrEpQRbA7ibaiQk1XOQlIftmBacA5s8jD8NvXn5W-rS832DOWHQS-G-j3N6U
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs `node preinstall.js` automatically during installation.
- The hook reads the machine hostname and OS username, then POSTs them to a hardcoded Discord webhook.
- The README confirms the data sent and says the hook runs on install; disclosure does not make the transfer opt-in.
Evidence against
- The README identifies the package as a security demonstration and warns users not to install it unless they understand its behavior.
- The hook writes a local marker recording the event and request result.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.preinstall = node preinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.preinstall = node preinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgpreinstall.jsView file
6L7: const WEBHOOK_URL = 'https://canary.discord.[redacted]-rS832DOWHQS-G-j3N6U';
L8:
...
L18: writeMarker = marker => fs.writeFileSync(
L19: path.join(__dirname, '.preinstall-marker.json'),
L20: JSON.stringify(marker, null, 2) + '\n'
...
L22: } = {}) {
L23: const message = `Run on ${os.hostname()} as ${os.userInfo().username} at ${timestamp()}`;
L24:
...
L26: package: 'cutekitten-test',
L27: event: process.env.npm[redacted] || 'manual',
L28: timestamp: new Date().toISOString(),
Critical
Findings
3 Critical3 High3 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationpreinstall.js
CriticalCredential Exfiltrationpreinstall.js
CriticalTrigger Reachable Dangerous Capabilitypreinstall.js
HighInstall Time Lifecycle Scriptspackage.json
HighFixed Authenticated Webhook Data Exfiltrationpreinstall.js
HighTrigger Reachable Credential Exfiltrationpreinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Low
Affected versions and remediation
This report applies to cutekitten-test@1.0.1.
See all versions of cutekitten-test for other recorded verdicts.
- Avoid installing cutekitten-test@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.