chalk-plus-ts
Copyright (c) React Training 2015-present
This report shows the evidence for chalk-plus-ts@1.0.4. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms an install-time detached remote-code loader with obfuscation and dynamic Function execution. This is concrete malicious behavior, not package-aligned Nodemailer network functionality.
Decision evidence
public snapshot- package.json defines postinstall: node lib/utils/index.js
- lib/utils/index.js spawns detached child process running lib/utils/smtp-connection/index.js
- lib/utils/smtp-connection/index.js is obfuscated and fetches https://api.jsonbin.io/v3/b/6a461991f5f4af5e295272d4
- Fetched JSON field record.cookie is executed with new Function(...)(require)
- lib/utils/smtp-connection/LICENSE is a 262624-byte hex/encrypted-looking blob colocated with the loader
- lib/nodemailer.js resembles bundled Nodemailer mailer functionality
- api.nodemailer.com and ethereal.email calls are user-invoked test-account functionality, not install-time
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
lib/utils/index.jsFindings
Affected versions and remediation
This report applies to chalk-plus-ts@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing chalk-plus-ts@1.0.4. 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.