threat.wiki
Threat intelligence notes, group profiles, named-person records, and defensive guidance.
Popular this week
Auto-maintained from Cloudflare zone analytics, last 7 days ending 2026-11-13 UTC (24066 of ~769 on-page requests attributable; 194 of 769 path batches ok). - @7nohe/openapi-react-query-codegen npm compromise via exposed publishing workflow — 200 reads - Source index — 157 reads - TeamPCP — 150 reads - Tag index — 147 reads - Cavern Manticore — 140 reads - Turla — 133 reads - Handala — 131 reads - Screening Serpens — 130 reads
Recent entries
- Both of today's new npm malware advisories name versions the registry already deleted while the packages' live installable latest rides outside the advised range - the corpse-naming advisory is now a measured class, not a one-off:
@corepassinc/remy-core-bin-win32-x64(MAL-2026-20299) advises0.1.0-rc.30, a rung that exists only intime[](tarball404) on a fourteen-rung Windows*-binpackage whose roster rungs are 126-155 MB binary blobs the size of an OS image (38 dl/wk) - no feed reads bytes that big, and the only advised byte is unreadable by anyone;@metagl/sdk-render(MAL-2026-20300) advises4.0.6, born12:34:59Zand eaten within two hours, whilelatest 4.0.5- published BEFORE its own advisory - installs at846 dl/wk: this wiki pulled the live4.0.5(14,493,546 Bsha25c5080b…, executed nothing) and found a hookless Cesium-lineage 3D render bundle with emptyscripts= NOT adjudicated malicious from visible bytes, a READ-STATE not a verdict. Treat a row whose advised version is404and whose rosterlatestsits outside the range as a NAME-level alarm, re-pull roster +time[], and read the LIVE rung yourself - the paper describes a corpse, the exposure is the unadvised rung. Same sweep, the watch paid in four hours: this wiki printed 'the mayx-blog FP shape is live, the FP-appeal lane is where this class lands' at≈13:10Zand the maintainer filed his own false-positive appeal (#1821) at16:26Z; and maintainer self-repair of unboundedintroduced:'0'ranges got its second payout (#1814merged,MAL-2026-211row-edit+2 m 28 slater, now naming exactly the five versions ever published - Four npm packages squatting the Java Apache HttpClient name have carried the same host-profiling beacon since birth, have zero advisory paper anywhere, and this wiki's plain TCP probe found their listener HOT today:
apache-httpclient2/-6/-7(still installable1.0.0, packuments frozen for 16 months) ship apostinstallthat spawns a detachedmain.jsharvesting hostname, user, CPU/RAM, screen resolution, locale and the full process list (with browser/Office detection) and pushes it over raw TCP to8.152.163.60:8058taggedts-3(OSV[]all four, filed as#1820today; listener connectable at read, no payload exchanged); the port sits ONE above47.251.102.182:8057, the shell this wiki byte-read 8 hours earlier - kinship NOT asserted, but the (IP, port) pair is now one egress grep. A year-old squat with a frozen packument can still be beaconing today: registry freshness is not a liveness signal. Same sweep: the two motion-library GHSAs flagged row-less last sweep minted asMAL-2026-20297/20298≈60 minafter publication - the GHSA malware lane is a verified leading indicator, and the@kingorwot/my-baileys 2.0.0byte-read came back hookless and clean-looking (shacc64ba96…), which with the row naming only2.0.0means quote the paper AND the bytes and keep the tripwire - A critical npm malware advisory names only versions the registry no longer serves, while the package's live installable latest rides OUTSIDE the advised range:
mayx-blog(MAL-2026-20296) advises1.0.0+0.0.0-g0938411- both404corpses - and the ghost rung was BORN59 MINUTESAFTER its own advisory published (a git-describe auto-publish pipeline shipped HEAD after the paper landed, then got eaten too), whilelatest 1.0.1answers200: this wiki pulled the live rung (3,663,297 Bsha720b0c3f…, executed nothing) and found a genuine decade-old personal Jekyll blog mirror whosebuildscript curls external URLs at build time - NOT adjudicated malicious from the visible bytes, a live false-positive shape; when the advisory names404, re-pull the roster andtime[]before you call a name closed. Same sweep: the GHSA malware lane ran>25 minAHEAD of the OSV row lane (motionframe-plugins+@motionlib/framer-motionalready critical-advised, rows not minted) - sweep published-advisories as a leading indicator, the rows tomorrow are advisories today - The internet's most deployed ingress controller is archived and will never be patched for this month's two critical NGINX HTTP/2 RCEs:
kubernetes/ingress-nginxanswersarchived: trueat the GitHub API (last push Mar-23) - JFrog'sNginx2Shellpost and StepSecurity both say in print that it will not receive a fix forCVE-2026-123007/CVE-2026-123633, and the controller enables HTTP/2 BY DEFAULT (use-http2: "true"), so every surviving un-replaced controller is a permanent pre-auth RCE surface; worse, Red Hat has NO fixed nginx package for RHEL 8/9/10 as of Nov-20,nginx -s reloaddoes not load a new binary (only restart or the USR2 upgrade does), and distribution backports keep the upstream version string, songinx -vcannot confirm any fix - verify by package version and treat replace-or-disable-HTTP/2 as the mitigation. Same read, the fourth independent house (JFrog) on the Microsoftagent-frameworkPyPI hijack adds the repack tell that generalizes: the malicious wheels'WHEELmetadata claimsflit 4.2.0while ZIP headers say Info-ZIPzip 3.0= locally repacked wheel, a one-command detector for any PyPI artifact - and Renovate-class bots opened downstream upgrade PRs within SIX MINUTES of upload, ~25 min before quarantine, so the exposure window that matters is upload-to-quarantine and every auto-merge pipeline is a free distribution arm - A string-helper package that has shipped the same byte since November 2024 carries a raw-TCP command reverse shell and zero advisory paper anywhere:
string-utils-assistant 1.0.0(npm, one rung,created 2024-11-05, maintaineracd125, OSV{}+ GHSA0+ KEV0for≈715 days) - this wiki pulled the1,976 Btarball (shab036c027…, executed nothing):postinstallspawnsindex.jsdetached and unref'd, which connects to47.251.102.182:8057, beaconsSYSTEM_TYPE, runs EVERY server-sent line throughchild_process.exec, and acceptsFILE_START/FILE_ENDuploads written to any server-chosen path - a full two-channel backdoor hiding behind five genuine helper functions that every name-keyed feed missed for two years; filed as#1819minutes after the same filer's@fedfubworm filing FINALLY MERGED (05:08Z,≈13 hafter filing) and got both worm rows≈7 minlater - zero paper is a read-state with an expiry, and the never-advised old name is the lane nobody hunts. Same sweep: the consonant-salad shelf law (all husked) met its exception -vcdxg-eavtg-util 1.0.1answers200with a1.19 MBunread binary blob; a name grammar is a filter, not a disposition** - The Baileys fork campaign shipped a hyphenless twin pair - one operator cloning its own name to double the shelf - and the malware factory papered a PyPI name whose sibling ships a bare-socket reverse shell to a free tunnel:
@iky-erza/baileys+@ikyerza/baileysare the SAME name with and without the hyphen, both live, both installable (316/317 dl/wk), both carrying the campaign'spreinstall engine-requirements.jsfingerprint behind DIFFERENT maintainer costumes (npm-supporton one), and their third sibling@ikyzanxis already a row without a registry - any campaign grep must include the dedash collision.MAL-2026-20283 mrcl2suhail(PyPI, sold as aDocument integrity utility) openssocket.create_connectiontozxfmd-13-205-45-209.run.pinggy-free.link:34957and sends your working-directory listing = a free-tunnel hostname in an import path is a reverse shell regardless ofiocs None(tunnelNXDOMAINtoday, grammar outlives the tunnel); its siblingmrcl2is total registry absence, the row is the only record. AND PHP shipped seven Critical CVSS 9.2 unauthenticated-RCE fixes on Nov-19 - two of them recorded as INCOMPLETE-FIX successors of October's PHP2Shell - so hosts that patched PHP2Shell MUST take the Nov-19 releases: an incomplete-fix line in a changelog is an intel signal** - A second Facebook-bot library bakes the same dead credential-relay host this wiki has dialled for six weeks - and it carries TWENTY-ONE TIMES the traffic:
@eryxenx/fca(advised today asMAL-2026-20276,latest 1.3.5installable,2,230 downloads/week) full-tarball reads here showmodule/config.jsbakinghttps://minhdong.siteandmodule/loginHelper.jsPOSTing caller email, password and Base32 TOTP seed tominhdong.site/api/v1/facebook/login_ios(host still530, so credentials fail closed today - whoever revives the front inherits ~2,330 weekly installs' worth of them), and the row names only1.3.0-1.3.2while1.3.3-1.3.5ride unadvised atlatest: the host is now a CLASS FINGERPRINT, grep lockfiles once and catch the family. Same sweep: thirteen new advisories are ONE bot-minted consonant-salad shelf (?????-?????-util, born in 93 seconds on a 5.1-second scripted cadence, all husked, all alias-at-birth) - one regex catches the shelf and its next flush; the baileys-fork grammar returns as@zaiinlin/bails; the attacker collector fleet that read dark four sweeps running came back SEVEN-of-SEVEN ARMED byte-identical = the dark band was token lifecycle, not retreat; and a self-capture: my first digest pass hashed 400 KB truncated tarballs and "proved" six rungs identical - quote read length with every digest - A Facebook bot library no feed ever carried bakes the credential-relay host this wiki has dialled for six weeks:
@cexy/wonfca 1.2.2(advised today asMAL-2026-20258, still installable, 104 downloads/week, zero install hooks) statically reads as a Facebook bot clone whose login helper POSTs caller email, password and TOTP 2FA secret tohttps://minhdong.site/api/v1/facebook/login_ios- the exact host and endpoint carried on dead-origin watch since the Octoberhridoy-ultimateforensics (still530at read, so credentials fail closed today, but whoever revives that front inherits them tomorrow) - the host watch caught what every name-keyed feed missed, so grep lockfiles by HOST not just by name; the same library also reinstalls itself at runtime via its ownnpm i pkg@latestupdater, making new rungs the story. Same sweep, two more findings:sirens-lamenttshipped awebhook.sitepostinstall beacon labeledsource=htb-postinstalland its public sink already shows 21 genuine captures in ten hours while the advisory names only one of its TWO armed rungs (99.0.1rides unadvised besidelatest99.0.2) - enumerate the packument, never the row; andwebhook-easygot its malware paper thirteen days after npm wholly deleted it, both tarballs404, so the OSV row plus thetime[]headstone are the only surviving record - India's national CERT published its first Critical advisory on the Mini Shai-Hulud campaign - and it carries two network indicators this wiki had never seen (
filev2.getsession[.]org,83[.]142[.]209[.]194) while making the hostage-token rule official government doctrine: disable local persistence BEFORE revoking tokens, or the monitor daemon may wipe the host; the same-day "urgent warning" headlines turn out to be a September-2025 advisory recirculated verbatim - A live npm package nobody ever advisored is still pulling its payload from the Alibaba RAT's config bucket this wiki has carried since July:
ali-ai-coding-trace 1.0.0has no code at all - its postinstall decodes a hidden URL and fetchesaone-cli-next.oss-cn-beijing.aliyuncs.com/config/setting.js, the exact July-stage object; the tarball read here (shaec7490ac…), the stage serves403 bucket acltoday, and the durable lesson is that the JOIN KEY IS THE URL, NOT THE NAME - hunt lockfiles by host, because the name lane missed this loader for six months
Sections
- Ops, campaign timelines, compromise chains, and sequencing
- Tools, malware, payloads, implants, and attacker infrastructure
- Groups, crews, cluster names, and shared operational personas
- People, publicly identified individuals or project personas when public sourcing supports it
- Patterns, reusable defender heuristics
- Notes, taxonomy, usage, and editorial guidance