Lucene search
+L

27 matches found

Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•5 views

Malicious code in quiche-tea-curut (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•7 views

Malicious code in dependent-final (npm)

Part of a self-republishing campaign: the package ships test.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•5 views

Malicious code in wet_rat_replicate_automation (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•6 views

Malicious code in unemployed_xerinae-toolteadev (npm)

Part of a self-republishing campaign: the package ships auto.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•3 views

Malicious code in pearx93qja-notthedevs (npm)

Part of a self-republishing campaign: the package ships autochange2.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fill...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•7 views

Malicious code in related_blackbird-toolteadev (npm)

Part of a self-republishing campaign: the package ships auto.js, which in a loop gives the package a new random name, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry worm and fills the...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•5 views

Malicious code in low_hummingbird_replicate_automation (npm)

Part of a self-republishing campaign: the package ships autopublish3.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•6 views

Malicious code in dian-peyek23-miaww (npm)

Part of a self-republishing campaign: the package ships auto.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•3 views

Malicious code in maila-talijah-alpha-128 (npm)

Part of a self-republishing campaign: the package ships loop.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a registry...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/05 6:34 a.m.•3 views

Malicious code in peas-tea-curut (npm)

Part of a self-republishing campaign: the package ships autopublish2.js, which in a loop gives the package a new random name, bumps its version, rewrites package.json and runs npm publish to publish the package again under the new name. Self-replicating publication is the propagation step of a...

6AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•4 views

Malicious code in sound_deer_apricot-15 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•5 views

Malicious code in temporary_smelt_lavender-81 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•5 views

Malicious code in valid_antlion_amber-50 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•4 views

Malicious code in pure_opossum_amaranth-54 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•5 views

Malicious code in intimate_ostrich_amethyst-45 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•9 views

Malicious code in unfortunate_crawdad_emerald-79 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•10 views

Malicious code in itchy_gecko_magenta-98 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•6 views

Malicious code in southern_duck_tan-16 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•5 views

Malicious code in xenacious_kangaroo_blush-47 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Github Security Blog
Github Security Blog
•added 2026/11/04 9:32 a.m.•4 views

Malicious code in smooth_angelfish_emerald-54 (npm)

Part of a self-republishing campaign: generated names of the form -, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies...

5.9AI score
SaveExploits0References2Affected Software1
Rows per page
Query Builder