maila-talijah-alpha-128@1.1.11
A Discord reporter for reports generated
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe 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.
Static reason
High-risk behavior combination matched malicious policy.
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.
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.
AI 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.
Evidence
loop.jspackage.jsonsrc/index.js
Network endpoints1
registry.npmjs.org/
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
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.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
UrlStrings
WildcardDependency
Source & flagged code
7 flaggedloop.jsView file
1const 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) {
Critical
Npm Publish Worm
Source mutates package metadata and republishes itself to npm.
loop.jsView on unpkg · L11const fs = require('fs');
L2: const { exec } = require('child_process');
L3:
High
30// Update the package name with the incremented number
const updatedPackageName = nameParts.join('-');
// Update the package name in package.json
p
High
Ai Review Evidence
loop.js changes the package name in package.json by incrementing its final numeric component.
loop.jsView on unpkg · L30Findings
1 Critical7 High2 Medium2 Low
CriticalNpm Publish Wormloop.js
HighChild Processloop.js
HighShell
HighAi Review Evidenceloop.js
HighAi Review Evidenceloop.js
HighAi Review Evidenceloop.js
HighSuspicious Lifecycle Evidencepackage.json
HighSuspicious Lifecycle Evidencesrc/index.js
MediumEnvironment Vars
MediumWildcard Dependency
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to maila-talijah-alpha-128@1.1.11.
See all versions of maila-talijah-alpha-128 for other recorded verdicts.
- 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.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.