
Research
/Security News
npm Package Uses Prompt Injection and Token Flooding to Disrupt AI Malware Scanners
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.
Bun-only CLI tool for llm-lean-log - Logging for LLMs, but we cut the fat.
llm-lean-logis a format for logging that is optimized for LLM token usage, using a simple CSV-based structure.
For more information, see the main repository.
bun add -g bl-log
For LLMs viewing logs (default output is structured CSV):
# List all log entries (returns CSV, omits empty columns)
l-log list ./logs/example.csv
# Show statistics
l-log stats ./logs/example.csv
# View detailed entry at index (returns minimal CSV)
l-log view ./logs/example.csv 0
# View the last log entry
l-log view ./logs/example.csv --last
# Search logs (returns CSV)
l-log search ./logs/example.csv "query"
# Filter by tags (returns CSV)
l-log tags ./logs/example.csv tag1 tag2
# Add a new log entry
l-log add ./logs/example.csv "Fix bug" --tags=bug,fix --problem="Problem description"
# Export logs to JSONL format
l-log export jsonl ./logs/example.csv --out=logs.jsonl
For human users viewing logs:
# List all log entries
l-log list ./logs/example.csv --human
# Show statistics
l-log stats ./logs/example.csv --human
# View detailed entry at index
l-log view ./logs/example.csv 0 --human
# Search logs
l-log search ./logs/example.csv "query" --human
# Filter by tags
l-log tags ./logs/example.csv tag1 tag2 --human
# Add a new log entry
l-log add ./logs/example.csv "Fix bug" --tags=bug,fix --problem="Problem description"
use l-log CLI to save chat log above
read last chat logs from "./logs/example.csv" and tell me what should I do next Example LLMs's response:
Based on the last entry in ./logs/example.csv and the current state of your repository, here is what you should do next:
### Current Status
The last task completed was "Make llm-lean-log packages public". This involved:
- Updating package.json for both llm-lean-log-core and l-log with repository info, files, and publishConfig.
- Adding LICENSE and README.md files.
- Configuring the CLI as an executable.
- Creating the guide at docs/public.md.
### Recommended Next Steps
1. Perform a Dry Run
Before pushing to NPM, ensure that the files being packaged are correct. Run this from the root:
...
bun run build
Output: "dist/l-log" file. Move "dist/l-log" to "/usr/local/bin/l-log-dev":
sudo mv dist/l-log /usr/local/bin/l-log-dev
This project was created using bun init in bun v1.3.5. Bun is a fast all-in-one JavaScript runtime.
.vscode/extensions.json, which includes:
DavidAnson.vscode-markdownlint - Markdown lintingbiomejs.biome - Code formatting and lintingoven-sh.bun - Bun runtime supportjeff-hykin.better-csv-syntax - CSV syntax highlighting (with color coding)YoavBls.pretty-ts-errors - Pretty TypeScript errorsMIT
FAQs
CLI tool for llm-lean-log and Bun only
We found that bl-log demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
A new npm package tests AI malware scanners with prompt injection, safety-triggering comments, context flooding, and obfuscated JavaScript.

Product
Socket now detects supply chain risks in project manifests, starting with missing lockfiles that can make dependency installs non-reproducible.

Research
/Security News
The trojanized extensions use TinyGo-compiled WebAssembly and Solana transaction memos to resolve command-and-control infrastructure.