calcurender
A lightweight utility for managing calculator UI instances and rendering optimizations.
This report shows the evidence for calcurender@1.0.0. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe entry point automatically decodes and executes a command embedded in the package manifest. The command downloads a batch file from an unrelated IP address and launches it, which is malicious remote code execution.
Decision evidence
public snapshot- The package declares main.js as its entry point and a start script that runs it.
- main.js runs main() at module load, so the command path is reached on import or when the start script runs.
- main.js XOR-decodes the package.json integrity value using the configured key; decoding the shipped value yields a command that downloads http://65.109.171.171/baseball.bat and launches it with cmd.
- The decoded command is passed to child_process.exec after a randomized delay of up to five seconds.
- On startup, main.js may also write a generated integrity value into package.json.
- The manifest declares no npm lifecycle hooks.
- The package has no declared dependencies. Its calculator utility description does not explain the decoded download-and-execute behavior.
Source & flagged code
7 flaggedThe package declares main.js as its entry point and a start script that runs it.
package.jsonView on unpkg · L1main.js XOR-decodes the package.json integrity value using the configured key; decoding the shipped value yields a command that downloads http://65.109.171.171/baseball.bat and launches it with cmd.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to calcurender@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing calcurender@1.0.0. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.