Search: “developer-morale”

AI slops from Eve

oss-security moderator Solar Designer approved three AI-generated vulnerability reports from automated security researcher Eve, sparking debate over AI slop on the list.

oss-security moderator Solar Designer approved three posts submitted by Eve, described as an 'automated security researcher', noting they lacked Date headers and arrived on the list server on September 9. He expressed uncertainty about their value but suggested they may have historical significance as early examples of AI-generated security reports at the dawn of AI security research. The post is meta-commentary on AI-generated content reaching a vulnerability disclosure mailing list rather than a specific vulnerability disclosure itself.

oss-security·updated Sep 13, 15:08 UTC · 2d ago·first Sep 10, 01:37 UTC · 6d agoIndustry 12 sources

My business partner sent a 5K vibe-coded PR that he didn't even test

A developer's business partner shipped a 5,236-line untested vibe-coded payments backend PR whose endpoints failed basic testing.

The author describes reviewing a pull request with 5,236 additions for a payments backend that a business partner generated largely with AI in a single day without testing. The PR's AI-written documentation included redundant boilerplate (e.g., 'returns 400 on error') but omitted operational details like where to obtain API keys, and the endpoints failed when tested. The post is a critical opinion piece on vibe coding and perceived skill atrophy among developers who rely on AI for everything.

Hacker News · security·Sep 8, 01:48 UTC · 8d agoAI industryHN 46↑ · 75 comments1

Feeling sad about AI

Simon Willison argues developers disheartened by AI coding agents should move past existential crisis and refocus on broader engineering problems.

In a comment on a Hacker News thread titled 'Feeling sad about AI', Simon Willison reflects on the discouragement engineers feel when AI coding agents complete in an hour work that previously took a week. He notes that translating an exact specification into decent code is no longer a unique skill. He counsels that engineers who accept this shift can apply their experience to the larger set of problems they still face.

Simon Willison·Sep 11, 17:28 UTC · 4d agoAI industry1

Closing the Blind Spot: Securing Personal Repositories in the Software Supply Chain

Wiz highlights personal developer repositories as a supply chain blind spot leaking corporate secrets, offering correlation-based risk validation and remediation.

Wiz argues that developers' personal code repositories are a blind spot in software supply chain security where corporate secrets quietly escape. The company describes an approach that correlates personal repositories to specific developers, validates the actual risk, and drives remediation. No specific incident or vulnerability is disclosed in the announcement.

Wiz Blog·Aug 13, 13:48 UTC · Aug 13, 2026Tools2

The Rise of the Forward Deployed Engineer — and How To Do the Job Right

Palantir veteran Vinoo Ganesh traces the forward deployed engineer role and shares practices for building effective FDE teams.

Kepler CEO and former Palantir forward deployed engineer Vinoo Ganesh argues that labs, startups, and PE firms hire FDEs without a shared definition of the role. He recounts Palantir's Project Frontline rotation, which trained about 250 software engineers as FDEs, many now leading forward deployed teams at OpenAI, Anthropic, xAI, and Anduril. A 2013 failure of the Phoenix transaction store at a bank, where real-world data gaps caused roughly 2.3 million keyspaces and an out-of-memory crash, illustrates why FDEs must own the gap between design and production reality. At Kepler he places the FDE function inside product rather than sales.

Latent Space·Sep 12, 15:01 UTC · 3d agoAI industry 4 sources1

AI supply chain risk is showing up in developer workflows first

Zentera Systems CEO says AI supply chain attacks currently hit developer workflows first, advising segmentation over tooling and citing the Phantom Raven campaign.

In an interview, Zentera Systems CEO Dr. Jaushin Lee argues that most active AI supply chain incidents target developer workflows and open-source package repositories, while poisoned model weights, compromised MCP servers, and poisoned vector stores remain largely in research and demos. He cites the active 'Phantom Raven' campaign, where attackers register AI-hallucinated package names in public repositories with malicious payloads that silently infect vibe-coding build pipelines. He recommends software-defined segmentation, semiconductor-style project enclaves with egress controls, and warns that self-hosting models without agent sandboxing leaves exposure unchanged.

Help Net Security·Aug 25, 00:00 UTC · 22d agoAI safety & security

curl: a CVE dispute

curl maintainer Daniel Stenberg details a dispute over a CVE assigned to the curl project.

Daniel Stenberg, lead maintainer of curl, published a post describing a dispute over a CVE affecting the project. The piece covers the vulnerability disclosure and CVE assignment process rather than a new exploitable flaw. Given curl's ubiquity, the process discussion is relevant to defenders tracking CVE quality, but no immediate risk is described.

Lobsters · security·Aug 31, 10:38 UTC · 15d agoVulnerability

Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain

Unit 42 warns attackers increasingly target CI/CD pipelines and developer tools rather than application code, urging full SDLC supply chain visibility.

Palo Alto Networks Unit 42 research argues attackers are shifting focus from application code to overlooked corners of the software development lifecycle supply chain, including CI/CD pipelines and developer tooling. The write-up calls for total SDLC visibility and strict security controls to defend these developer-facing attack surfaces.

Palo Alto Unit 42·Aug 21, 23:00 UTC · 25d agoResearch in the wild

"They don't care about this": A Systematic Study of TEE Build Reproducibility in the Wild

91% of 115 surveyed TEE deployments across Intel SGX, TDX, and AMD SEV fail to provide reproducible builds needed for verifiable remote attestation.

A systematic study of 115 TEE deployments found 91% were not reproducible and 80% lacked both source code and a reference build, undermining remote attestation guarantees. Interviews with 12 developers of 50 Intel SGX projects confirmed that only one participant treats reproducibility as a development priority. The authors identify technical barriers such as embedded timestamps plus ecosystem-level issues like lack of build-environment control in multi-stakeholder projects, and call for holistic, committed reproducibility practices.

arXiv cs.CR·Sep 10, 11:43 UTC · 5d agoResearch

Understanding Operator Attitudes Toward AI-Supported Decision Making in Maritime Operations

A survey of maritime professionals finds positive but scenario-sensitive attitudes toward AI collision-avoidance assistants, urging design for calibrated reliance.

The study surveyed maritime stakeholders on attitudes toward AI-supported collision-avoidance assistants for Maritime Autonomous Surface Ships, measuring technology anxiety, trust in automation, and explanation quality with established questionnaires plus thematic analysis of open responses. Results show generally positive disposition, no clear age-related openness differences, stable trust across scenarios, and multidimensional, scenario-sensitive explanation ratings. Participants valued decision support and situation awareness but worried about AI reliability, over-reliance, and skill loss; the authors recommend designing for calibrated reliance with domain experts in the loop rather than maximizing automation or trust.

arXiv cs.AI / cs.LG / cs.CL·Sep 10, 16:57 UTC · 5d agoAI research1

Senior engineers are spending their week cleaning up AI-generated code

New Relic study finds AI-generated code doubles critical runtime issues, with senior engineers losing a third of their week to fixes.

A New Relic survey of U.S. technology leaders reports AI now writes the majority of shipped code, with senior SRE and DevOps engineers spending up to a third of their week triaging and refactoring it. A large majority of organizations had at least one AI-related production failure in the past six months, and roughly three in ten saw newly introduced security vulnerabilities. AI-generated code showed nearly twice as many critical runtime issues as peer-reviewed human-authored code, with gaps concentrated in edge cases, concurrency, deprecated APIs, and complex state changes. Most teams now prompt AI tools to embed logs and traces directly into generated code.

Help Net Security·Aug 24, 04:22 UTC · 23d agoAI industry1

Can your coding style predict whether your code is vulnerable?

University of Massachusetts Dartmouth researchers present VulStyle, a stylometry-based vulnerability detector that also exposes benchmark reliability problems.

VulStyle combines stylometric features with syntax-tree structure and source tokens, pre-trained on about 4.9 million functions across seven programming languages and fine-tuned on five vulnerability detection datasets. It beat token-only detectors on some benchmarks but its F1 drops sharply on DiverseVul, which the authors link to noisy labels inflating reported performance across popular datasets. The authors argue style-aware detection should be harder to evade but did not test this empirically, and they note that uniform LLM-generated code may strip away the individual developer style the model depends on.

Help Net Security·Aug 24, 04:21 UTC · 23d agoResearch1

Everyone should slow down AI development except for me

Opinion essay satirizing AI developers who advocate slowing AI development while continuing their own work; 101 points on Hacker News.

Xe Ito's essay titled 'Everyone should slow down AI development except for me' comments on AI development pacing and slowdown debates. The piece drew 101 points and 14 comments on Hacker News. No technical security or policy details are provided in the source metadata.

Hacker News · security·Sep 13, 00:30 UTC · 3d agoAI policyHN 101↑ · 14 comments1

τ^τ-Bench: An Environment for End-To-End, Realistic Agent Construction

New τ^τ-bench tasks coding agents with building deployable customer-service agents; best config, Claude Opus 5, passes only 23.9% of simulations.

Researchers introduce τ^τ-bench, an end-to-end benchmark where a developer agent must build a complete customer-service agent from real business records, a client with requirements, a production API, an inherited codebase, and cost/model limits, then is scored by deploying it against held-out simulated users. Across 53 tasks in four domains, the strongest configuration, Claude Opus 5 under Claude Code, passes just 23.9% of evaluation simulations versus an 82.2% expert-authored reference ceiling. Failure modes mirror those of human developers: shallow queries instead of deep record comprehension, almost no client communication, and shipping the first architecture that runs rather than experimenting.

Hugging Face daily papers·Sep 3, 20:00 UTC · 12d agoAI research

Give Your Coding Agents a Memory You Own

Hugging Face introduces Funes, a tool that gives coding agents persistent, self-owned memory outside vendor clouds.

A Hugging Face blog post presents Funes, an approach for giving coding agents a persistent memory that developers own and control. The piece targets agent workflows where context must survive across sessions without ceding data to third-party services. No article body was available in the feed, so specifics beyond the title are limited.

Hugging Face Blog·Sep 3, 00:00 UTC · 13d agoAI tools & infra1

Legit Security VibeGuard 2.0 brings endpoint security and real-time guardrails to AI coding agents

Help Net Security·Aug 4, 00:00 UTC · Aug 4, 2026AI safety & security

VU#456290: Hugging Face Transformers library writes remote code to disk prior to consent check

CVE-2026-80047: Hugging Face Transformers 4.49.0 through 5.8.1 writes attacker-controlled Python files to disk before the trust_remote_code consent check.

CERT/CC vulnerability note VU#456290 describes CVE-2026-80047 in the Hugging Face Transformers library, affecting versions 4.49.0 through 5.8.1. The library performs a remote module fetch and writes attacker-controlled Python files to the local disk before evaluating the trust_remote_code consent prompt, without user authorization. This violates the security contract enforced across other dynamic module-loading paths in the library. Transformers is a primary framework for training and inference across NLP, vision, audio, video, and multimodal machine learning systems.

CERT/CC Vulnerability Notes·Sep 1, 13:35 UTC · 14d agoVulnerabilityCVE-2026-800471

How Developers Prevent Production Risk at the Source

Wiz argues shift-left code-stage security cuts remediation costs and ships Wiz Code, WizOS, and WizCLI to catch flaws pre-deployment.

A Wiz blog post argues that fixing vulnerabilities at the code stage costs a fraction of production remediation, citing the node:20-slim base image which ships 14 known CVEs, three of them critical. It claims AI agents can now analyze open-source commits and generate working exploits in minutes, shrinking the window between a public fix and automated attacks. The post promotes WizOS near-zero-CVE base images, WizCLI and MCP-server checks inside developer and AI agent sessions, and Wiz Code scanning across pull requests, repositories, and pipelines covering SAST, SCA, secrets, and IaC misconfigurations.

Wiz Blog·Sep 3, 00:31 UTC · 13d agoIndustry1

When Vibe Hacking Turns AI into the Junior Hacker Every Adversary Always Wanted

The Hacker News·Aug 4, 11:30 UTC · Aug 4, 2026Vulnerability

Ubuntu 24.04.5 LTS release patches security bugs across ten flavors

Canonical ships Ubuntu 24.04.5 LTS point release bundling security fixes into fresh install media for desktop, server and nine other flavors.

Canonical released Ubuntu 24.04.5 LTS, a point release for the Noble Numbat series that folds accumulated security corrections and high-severity bug fixes into new installation media. Nine flavors including Kubuntu, Xubuntu, Ubuntu MATE, Ubuntu Studio and Edubuntu also moved to 24.04.5. Existing 22.04 LTS users receive the fixes through the automatic upgrade path at no cost. The release notes name no CVEs or bug IDs, and support timelines still count from the original 24.04 launch date (five years for Desktop/Server/Cloud/Core, three for flavors, extendable with Expanded Security Maintenance).

Help Net Security·updated Sep 11, 12:03 UTC · 4d ago·first Sep 11, 04:07 UTC · 5d agoAdvisory 13 sources

Quoting Laurie Voss

Laurie Voss argues AI collapses code-writing and review costs, leaving product discovery and precise definition as the core of software engineering.

Simon Willison quotes Laurie Voss's essay "We are all Product Engineers now," which argues that AI is collapsing the cost of writing code and will likewise collapse the cost of reviewing, fixing, and operating it. Voss contends the remaining work is finding out what people want, defining it precisely, and making software pleasant to use. He expects the amount of software to grow without limit because demand has no ceiling, making product-definition skills the whole job. No specific models, tools, or incidents are named; this is career and industry commentary.

Simon Willison·Sep 14, 14:34 UTC · 1d agoAI industry

How to Investigate GitHub PAT Compromise: Lessons From a Multi-Organization Campaign

Wiz CIRT published an investigation playbook for GitHub PAT compromise after responding to a coordinated multi-organization campaign.

Wiz's Computer Incident Response Team shared lessons from its response to a coordinated campaign compromising GitHub personal access tokens across multiple organizations. The post provides a practical playbook covering detection, scoping, and investigation steps for token compromise. Specific victim names, affected counts, and attribution are not provided in the announcement.

Wiz Blog·Aug 13, 15:04 UTC · Aug 13, 2026Threat actor in the wild1

Dr. Claw: An AI Scientist Workspace for Vibe Research

Researchers release Dr. Claw, an open-source auditable workspace that wraps coding agents like Claude Code for end-to-end AI-assisted research workflows.

Paper 2609.00365 presents Dr. Claw, an open-source workspace that wraps existing coding-agent executors such as Claude Code and Gemini CLI in a controllable, human-in-the-loop research workflow. It uses persistent state objects, a reusable skill library, and multi-executor coordination to make research decisions auditable and recoverable, rather than adding another autonomous agent. Holding the executor fixed, Dr. Claw scores higher on research completeness than a bare command-line agent while preserving an auditable process trail. The code is released under AGPL-3.0 on GitHub (OpenLAIR/dr-claw).

Hugging Face daily papers·Aug 30, 20:00 UTC · 16d agoAI research

An Empirical Analysis of CodeQL False Positives and Query Refinements for Java Vulnerabilities

Study of 167 Java CVE instances finds CodeQL false positives follow recurring patterns; query refinements remove 81.8% of reviewed ones.

Researchers ran CodeQL's Java security query suite on 167 CVE instances from 110 projects, manually reviewing 500 sampled false-positive paths and building a five-category taxonomy led by Missed Path Constraint or Sanitization (36.6%), Benign Execution Context (29.4%), and Missing Trust Boundary Modeling (27.6%). Guided by the taxonomy, query-level refinements removed 81.8% of reviewed false positives and 15.8% of reported paths across the selected queries while retaining 7 of 8 true positives. To address generalization, agentic coding tools given the refinement patterns as templates adapted them to new projects successfully in 56% and 62% of tasks, versus 28% without guidance.

arXiv cs.CR·Sep 3, 22:48 UTC · 12d agoResearch1

Enabling Creative Exploration for Vibe Design Agents

Separating design-direction exploration from code generation via structured specifications broadens UI alternatives without destabilizing output.

The paper proposes an inference architecture for vibe design agents that makes design direction an explicit intermediate decision: a Verbalized Sampling-inspired pre-pass proposes structured design specifications with typicality scores, an external selector samples one, and a downstream generator realizes it under fixed settings. Across 168 prompts with 1,255 paired comparisons per temperature, theme sampling broadens selection coverage and screenshot variation, with LLM-judge preferences varying across interventions and prompt complexity. An online experiment with over 300,000 tasks found the code-export increase statistically uncertain, though negative feedback events decreased alongside modest operational costs.

Hugging Face daily papers·Sep 13, 20:00 UTC · 2d agoAI research

Version Control DFIR: a Cheatsheet to GitHub, GitLab, Bitbucket, and Azure DevOps

Wiz published a DFIR cheatsheet covering log visibility, incident readiness, and threat hunting across GitHub, GitLab, Bitbucket, and Azure DevOps.

Wiz researchers released a practitioner's guide to version control system forensics, incident response, and threat hunting. The cheatsheet maps log sources, audit capabilities, and hunting workflows across GitHub, GitLab, Bitbucket, and Azure DevOps. It aims to improve incident readiness for source code and CI/CD compromise scenarios.

Wiz Blog·Aug 27, 12:00 UTC · 19d agoResearch1

[0day-rubbish] core-admin 1.0.164 (build 16468) Systemic shell command injection via ineffective quote escaping (8.8)

0day Rubbish discloses a CVSS 8.8 shell command injection in core-admin 1.0.164 via ineffective quote escaping, enabling authenticated remote code execution.

0day Rubbish Research Team publicly disclosed a systemic shell command injection (CWE-78) in core-admin 1.0.164 (build 16468). The flaw stems from ineffective quote escaping and scores 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The disclosure does not mention a CVE identifier or observed exploitation in the wild.

Full Disclosure·Sep 8, 17:31 UTC · 7d agoVulnerability1

Debian developers rejected an LLM ban and left disclosure voluntary

Debian developers voted to encourage voluntary disclosure of AI assistance in contributions rather than banning or mandating labeling of LLM-generated code.

Debian's vote concluded August 28, with project secretary Kurt Roeckx announcing that the winning option encourages contributors to disclose generative AI assistance and stops there, adding no new mandatory review gates. The adopted resolution bars sending confidential material, embargoed security bugs, cryptographic keys and credentials to third-party AI services without explicit authorization, requires prior discussion for bulk automated work, and takes no position on whether model output is copyrightable. The project neither endorses nor prohibits generative AI and retains existing human review and licensing requirements.

Help Net Security·Aug 31, 00:00 UTC · 16d agoAI policy