demo-awesome-date-parser-test
This report shows the evidence for demo-awesome-date-parser-test@0.0.3. 7 of 7 known versions are blocked or flagged. The newest version, 0.0.7, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms malicious runtime behavior behind the package’s exported date parser. Lack of lifecycle hooks limits installation-time exposure but does not mitigate the activated browser payload.
Decision evidence
public snapshot- src/index.js is heavily obfuscated and exposes a date-parser export.
- demoParseDate() invokes injectScriptIfNeeded() at runtime.
- Injected logic captures form name/email/message values and stores them in localStorage.
- It exfiltrates captured values with fetch and unload sendBeacon calls.
- It dynamically executes eval, Function, setTimeout strings, and import().
- It downloads an embedded PDF and overwrites clipboard text.
- package.json has no preinstall/install/postinstall hooks.
- No child-process or local filesystem behavior was found.
Source & flagged code
3 flagged · loading sourceSource contains an obfuscator-style string-array loader that reconstructs and executes hidden code.
src/index.jsView on unpkg · L1Package source references dynamic require/import behavior.
src/index.jsView on unpkg · L1Package source references a known benign dynamic code generation pattern.
src/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to demo-awesome-date-parser-test@0.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing demo-awesome-date-parser-test@0.0.3. 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.