pkgscan.dev · Security Advisories
Package Security Advisories & Scan Reports
pkgscan.dev tracks malicious, impersonating, vulnerable, and removed packages across npm, PyPI, NuGet, Maven, Go, Cargo, RubyGems, Open VSX, the VS Code Marketplace, and agent-skill registries. Each entry names the flagged package, the affected version when known, its registry, the reason it was flagged, and a link to the scan report where available.
The list is newest first. Search or filter by registry to narrow it, or open a package report for scan findings, advisory IDs, and the underlying evidence. The date in the left column is when the advisory was published or updated — not when the package was uploaded to its registry, and not when you installed it.
Latest advisories
- [MALWARE] [email protected] (vscode-marketplace) — REMOTE_PAYLOAD
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — Malicious code in lwd_uri_util (crates.io)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — CREDENTIAL_THEFT
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — Malicious code in lwd_uri_util (crates.io)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @yshtxxproject/baileys (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Detects npm preinstall scripts, which are almost exclusively used for malware delivery
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — OBFUSCATED_CODE
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @yshtxxproject/baileys (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in sauruspro-bail (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (vscode-marketplace) — DATA_EXFILTRATION
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @zanxiky/baileys (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @zanxiky/baileys (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @postex/common (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @postex/common (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fcsmc/commercial-analytics (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fcsmc/commercial-analytics (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fmr-ap149494/apex-base-component (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fmr-ap149494/apex-base-component (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @futurae-public/adaptive-js (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @futurae-public/adaptive-js (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @generic-means/ing-feat-scanner-libs (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @factoryz/apollo (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in nodecheck-health (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @jm-telefonica/multibrand-components (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @generic-means/ing-feat-scanner-libs (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @factoryz/apollo (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @jm-telefonica/multibrand-components (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fmr-ap153177/apex-kit-icons (npm)
scan · advisory 2026-11-10 - [MALWARE] @[email protected] (npm) — Malicious code in @fmr-ap153177/apex-kit-icons (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in nodecheck-health (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in npm-scanner (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in moltbook-health (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in npm-scanner (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — Malicious code in lwd_uri_util (crates.io)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in moltbook-api-helper (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in moltbook-health (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — Malicious code in lwd_uri_util (crates.io)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_frau_holle_die_nordische_gottin_hulle_und_ihr_gef_by_holger_karsten_schmid_1u2dk@0.0.1-security (npm) — Malicious code in dowload_ebok_frau_holle_die_nordische_gottin_hulle_und_ihr_gef_by_holger_karsten_schmid_1u2dk (npm)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_ho_mangiato_abbastanza_by_giorgio_serafini_prosperi_txkvg@0.0.1-security (npm) — Malicious code in dowload_ebok_ho_mangiato_abbastanza_by_giorgio_serafini_prosperi_txkvg (npm)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_ho_mangiato_abbastanza_by_giorgio_serafini_prosperi_txkvg@0.0.0-stage (npm) — Malicious code in dowload_ebok_ho_mangiato_abbastanza_by_giorgio_serafini_prosperi_txkvg (npm)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_frau_holle_die_nordische_gottin_hulle_und_ihr_gef_by_holger_karsten_schmid_1u2dk@0.0.0-stage (npm) — Malicious code in dowload_ebok_frau_holle_die_nordische_gottin_hulle_und_ihr_gef_by_holger_karsten_schmid_1u2dk (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — deps.dev: cooldown
scan · advisory 2026-11-10 - [VULNERABILITY] [email protected] (npm) — deps.dev: malicious
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_la_ternura_de_dios_by_papa_francisco_kq4hn@0.0.0-stage (npm) — Malicious code in dowload_ebok_la_ternura_de_dios_by_papa_francisco_kq4hn (npm)
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — Malicious code in lwd_uri_util (crates.io)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_mein_fur_immer_by_b_h_bartsch_jjche@0.0.1-security (npm) — Malicious code in dowload_ebok_mein_fur_immer_by_b_h_bartsch_jjche (npm)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_la_ternura_de_dios_by_papa_francisco_kq4hn@0.0.1-security (npm) — Malicious code in dowload_ebok_la_ternura_de_dios_by_papa_francisco_kq4hn (npm)
scan · advisory 2026-11-10 - [MALWARE] npm.dowload_ebok_la_historia_universal_en_100_preguntas_by_luis_e_inigo_fernandez_0w097@0.0.1-security (npm) — deps.dev: cooldown
scan · advisory 2026-11-10 - [MALWARE] [email protected] (cargo) — ENV_HARVESTING
scan · advisory 2026-11-10 - [MALWARE] [email protected] (npm) — Malicious code in dowload_ebok_ulysse_by_james_joyce_2tbxz (npm)
scan · advisory 2026-11-10
How pkgscan scans a package
Scans run through SCINTX, an open-source detection gateway. pkgscan is the consumer: it handles sign-in, scan quota, queueing, durable storage, and the public report. SCINTX owns the providers and routes each artifact to the engines that support its type.
Content scanners such as Argus, GuardDog, and SkillSpector inspect the artifact for malware, risky install scripts, and prompt injection. Vulnerability matchers such as OSV, Grype, and deps.dev compare the package identity against public advisories. Every report lists the engines that ran, each engine's verdict, the findings it returned, and when the scan completed. Engines that do not support an artifact type are marked unsupported rather than counted as clean.
What the categories mean
- Malware — the package was published to run malicious code, steal credentials, or install a payload.
- Impersonation / typosquat — the name imitates a trusted package or publisher to capture installs.
- Vulnerable — the version carries a known vulnerability from a CVE, GHSA, or OSV advisory. The package itself is not necessarily malicious.
- Untrustworthy — the publisher or a linked domain no longer supports a trustworthy install, for example an expired domain.
- Removed, deprecated, copyright, or spam — the package was withdrawn or does not provide the software it claims to.
How to read a scan verdict
Each report shows the engines that ran and what each one returned. Malicious or flagged means at least one engine found malware or a high-risk pattern; treat the package as unsafe. Suspicious or warn means something needs review. Clean or pass means no engine flagged the artifact at scan time, which is not a guarantee. Unsupported, pending, or error is not a clean result.
For a malware advisory, remove the version and rotate any credentials the package could read. For a vulnerability advisory, check the affected range and upgrade to a fixed version. A scan describes the artifact that was scanned; it does not know what is installed on your machine. For VS Code extensions, DevGuard checks installed extensions against this feed. For a one-off check, paste a package URL or file hash into the scanner.
How this feed is built
Entries come from registry metadata, the Open VSX changes feed, Microsoft's removed-packages list, vulnerability databases including OSV, CVE, and GHSA, and scan findings produced through SCINTX. New advisories are added as they are ingested; reports are updated when an advisory ID, verdict, or classification changes.
Coverage is not exhaustive. A package that is not listed may still be malicious or vulnerable, and a clean scan only describes the artifact that was scanned. Treat this feed as a starting point for verification, not a guarantee. The API documentation explains how to query the same data programmatically, and live provider health is on the status page.
Frequently asked questions
Does a listed advisory mean my project is compromised?
No. An advisory records that a package or version was flagged by a scan or a registry feed. Whether your project used it, and whether it could do harm there, depends on your lockfile, install history, and runtime. Confirm the exact version before acting.
Why is a package still listed after it was removed?
The advisory is a historical record. Removing a package from a registry stops new downloads; it does not undo installs that already happened. The report keeps the advisory and its evidence so the decision can be audited later.
What is the difference between malicious and vulnerable?
A malicious package is intended to cause harm. A vulnerable package is legitimate software with a known security flaw. Both can be dangerous, but the response differs: remove malicious packages and rotate exposed credentials; patch or upgrade vulnerable ones.
What runs the scans?
Scans run through SCINTX, the open-source detection gateway that pkgscan uses. SCINTX owns the providers and routes each artifact to the engines that support its type; pkgscan handles the account, queue, storage, and public report. Live provider health is listed on the status page.
How often is the list updated?
Advisories are written when a scan or registry feed produces a publishable finding, and reports are updated when an advisory ID, verdict, or classification changes. The list is not a real-time mirror of every registry.