--- canonical: "https://firewall.lpm.dev/npm/maila-talijah-alpha-128" markdown: "https://firewall.lpm.dev/npm/maila-talijah-alpha-128/report.md" package: "maila-talijah-alpha-128" report_status: "published" title: "maila-talijah-alpha-128@1.1.11 npm security report" verdict: "malicious" version: "1.1.11" --- # maila-talijah-alpha-128@1.1.11 npm security report > **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document. ## Verdict summary **Blocked & quarantined** — With npm publishing credentials available, it can publish repeated package-name variants without further confirmation. - **Verdict:** Malicious - **Product-default install policy:** Block - **Firewall policy:** Block by default - **Public report status:** Published - **Threat category:** Malware - **Selected version:** 1.1.11 - **Selected version is latest:** Yes - **Analysis source:** AI Security Review (lpm-firewall-ai) LPM AI independently confirmed malicious behavior in this version and supplies the Firewall block. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. The package contains a purpose-unrelated script that repeatedly renames and publishes packages to the public npm registry. Although the manifest does not invoke it automatically, running the script starts an unbounded publishing cycle, which is concrete malicious behavior. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 98.0% - **Started:** 2026-11-05T06:54:51.963Z - **Finished:** 2026-11-05T06:55:26.523Z - **Download time:** 512 ms - **Static scan time:** 22 ms - **AI review time:** 34025 ms - **Total time:** 34560 ms The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs. ## Security analysis ### Published attack-surface review - **Summary:** A standalone script mutates package metadata and repeatedly publishes under incremented package names. - **Trigger:** Running loop.js starts the cycle; it is not referenced by the declared main or bin entry points or a lifecycle script. - **Impact:** With npm publishing credentials available, it can publish repeated package-name variants without further confirmation. - **Evidence paths:** loop.js, package.json, src/index.js - **Review source:** ai\_review - **Reviewed:** 2026-11-05T06:55:26.523Z ### AI review details - **Review stage:** source\_first\_review - **Mechanism:** It rewrites package.json, invokes \`npm publish --access public\`, and schedules another cycle every six seconds. - **Attack narrative:** When explicitly run, loop.js increments the package name in package.json, publishes it publicly through npm, and repeats the process every six seconds, enabling uncontrolled publication of package variants. - **Rationale:** The package contains a purpose-unrelated script that repeatedly renames and publishes packages to the public npm registry. Although the manifest does not invoke it automatically, running the script starts an unbounded publishing cycle, which is concrete malicious behavior. - **Files touched:** package.json - **Network endpoints:** https://registry.npmjs.org/ ### Review decision - **Verdict:** Malicious - **Confidence:** 98.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **Evidence for block:** loop.js changes the package name in package.json by incrementing its final numeric component., loop.js runs \`npm publish --access public\`., After publishing, loop.js schedules the same name-change and publish cycle to repeat every six seconds., The manifest points its main and bin entry points to src/index.js and defines no lifecycle scripts; the publish loop is not part of those declared entry points. - **Evidence against:** The declared CLI entry point runs a test-reporting workflow and sends the report to a Discord webhook supplied by the user or environment. ## Affected versions and remediation This report applies to maila-talijah-alpha-128@1.1.11. - Avoid installing maila-talijah-alpha-128@1.1.11. 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. ## Public findings ### 1. High: Child Process - **Category:** Source - **Confidence:** 85.0% - **Path:** loop.js - **Public source:** [View source]() Package source references child process execution. Public source snippet (untrusted): ```javascript L1: const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ``` ### 2. High: Shell - **Category:** Source - **Confidence:** 85.0% Package source references shell execution. ### 3. Medium: Environment Vars - **Category:** Source - **Confidence:** 75.0% Package source references environment variables. ### 4. Low: Filesystem - **Category:** Source - **Confidence:** 70.0% Package source references filesystem APIs. ### 5. Critical: Npm Publish Worm - **Category:** Source - **Confidence:** 90.0% - **Path:** loop.js - **Public source:** [View source]() Source mutates package metadata and republishes itself to npm. Public source snippet (untrusted): ```javascript L1: const fs = require('fs'); L2: const { exec } = require('child_process'); L3: L4: // Function to increment the version in package.json L5: function incrementPackage() { ... L7: // Read package.json L8: const packageJson = JSON.parse(fs.readFileSync('package.json', 'utf8')); L9: ... L46: function publishPackage() { L47: exec('npm publish --access public', (error, stdout, stderr) => { L48: if (error) { ``` ### 6. Low: Url Strings - **Category:** Supply Chain - **Confidence:** 65.0% Package source contains URL literals. ### 7. Medium: Wildcard Dependency - **Category:** Manifest - **Confidence:** 80.0% Package manifest contains a wildcard dependency. ### 8. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** loop.js - **Public source:** [View source]() loop.js changes the package name in package.json by incrementing its final numeric component. Public source snippet (untrusted): ```javascript // Update the package name with the incremented number const updatedPackageName = nameParts.join('-'); // Update the package name in package.json p ``` ### 9. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** loop.js - **Public source:** [View source]() loop.js runs \`npm publish --access public\`. Public source snippet (untrusted): ```javascript // Function to publish the package function publishPackage() { exec('npm publish --access public', (error, stdout, stderr) => { if (error) { console.error('Error publishing package:', er ``` ### 10. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** loop.js - **Public source:** [View source]() After publishing, loop.js schedules the same name-change and publish cycle to repeat every six seconds. Public source snippet (untrusted): ```javascript // Function to run increment and publish in a loop function runLoop() { // Increment package name and publish package incrementPackage(); publishPackage(); // Delay for 1 minute (adjust as needed) se ``` ### 11. High: Suspicious Lifecycle Evidence - **Category:** Manifest - **Confidence:** 98.0% - **Path:** package.json - **Public source:** [View source]() The manifest points its main and bin entry points to src/index.js and defines no lifecycle scripts; the publish loop is not part of those declared entry points. Public source snippet (untrusted): ```json { "name": "maila-talijah-alpha-128", "version": "1.1.11", "description": "A Discord reporter for reports generated", "main": "src/index.js", "bin": { "maila-talijah-alpha": "src/index.js" }, "repository": { "type": "git", "url": "https://github.com/dlordkendex/maila-talijah ``` ### 12. High: Suspicious Lifecycle Evidence - **Category:** Manifest - **Confidence:** 98.0% - **Path:** src/index.js - **Public source:** [View source]() The manifest points its main and bin entry points to src/index.js and defines no lifecycle scripts; the publish loop is not part of those declared entry points. Public source snippet (untrusted): ```javascript #!/usr/bin/env node const maila = require('maila') const { compileResults } = require('./compileResults') const { sendWebhook } = require('./di ``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** No - **Dependencies:** 5 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 5 ### Published dependency entries - @dlordkendex/maila-discord-reporter \* (Dependency) - discord-webhook-node ^1.1.8 (Dependency) - dotenv ^8.2.0 (Dependency) - foever \* (Dependency) - pm2 \* (Dependency) ## Package metadata - **Package:** maila-talijah-alpha-128 - **Ecosystem:** npm - **Version:** 1.1.11 - **License:** ISC - **Version published:** 2024-04-02T12:15:26.630Z - **Package first seen:** 2026-11-05T06:55:26.523Z - **Package last seen:** 2026-11-05T06:55:26.523Z - **Known versions:** 1 - **Latest version:** 1.1.11 - **Appeal under review:** No - **Description:** A Discord reporter for reports generated - **Author:** dlord - **Keywords:** maila, talijah - **Artifact files:** 16 - **Artifact unpacked size:** 132,950 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]() - [Repository]() - [Homepage]() - [Issues]() - [OpenSSF/OSV advisory]()