❌

Reading view

Anthropic Reveals Fourth Likely Crime Committed By Its AI

An anonymous reader quotes a report from The Register: Amid industry soul-searching about the possibility of AI improving itself to the point that it kills everyone, Anthropic has revealed yet another incident that would qualify as a crime if perpetrated by a person. The AI biz published "an alignment assessment" detailing four times Claude models accessed third-party systems without authorization. The company has already reported three of the incidents. Evidence of the fourth was lurking in a session transcript dating back to January 2026 when the misbehavior occurred. Anthropic found the first three by scanning around 141,000 transcripts where Claude could have obtained internet access during evaluation. It missed the fourth initially because "our scan relied on an agentic search." [...] The January 2026 AI trespass involved an early version of Claude Opus 4.6, which was given a Capture the Flag (CTF) challenge under the oversight of the third-party model evaluator where the other hacking events occurred. Opus 4.6 managed to sabotage its chances of success by disabling the machine it was targeting. It assigned the device an IP address that already existed on another piece of hardware, rendering the target unreachable and making it impossible to solve the challenge. Those familiar with other incidents where AI models violated third-party systems may recall that unsolvable tasks represent a common catalyst for misbehavior. Models exhaust all aligned options, and then turn to transgressive approaches. Opus 4.6 might have been an exception, but when it tried to abort the task after recognizing that it could not reach the target machine, it failed to do so "due to a misconfiguration in [the model's] evaluation harness." It failed to shut down not just once but seven times. So it continued onward, trying other expected means to reach the target machine but failing. Then it explored further. "The model discovered a machine belonging to a third party that it was able to access, and stated that it believed this third party was part of the CTF," Anthropic explained in its post. "Inside the machine, the model found a file listing a password, which it used to gain admin access to the system." The model went on to gather more credentials, and modified a system setting to make it easier to access the personal information of an individual associated with the third party evaluation organization. Opus 4.6 might have done more but for the fact that it exhausted its token budget, bringing the session to an end. Anthropic says it's not as concerned about this incident as the others because the model tried to abort its task.

Read more of this story at Slashdot.

  •  

Google to Invest Record $15 Billion In AI Infrastructure In Finland

Google plans to invest at least $15 billion in AI infrastructure in Finland through 2028, its largest single investment in Europe. The company also signed a 22-year power agreement with Finnish utility Fortum and said it will explore business models that could support new nuclear reactors at Fortum's Loviisa site. Finland has emerged as a major data-center hub thanks to its available land and power. "I've heard it called the 'Texas of Europe' at industry events," Matti Lajunen, partner of real estate at Finnish law firm Hannes Snellman, told CNBC. "What we're now seeing is weekly new inquiries for market entry into Finland from new players." Ruth Porat, president and chief investment officer of Alphabet and Google, said in a statement: "Google is proud to deepen our roots in Finland with the company's largest single investment in Europe, building on more than 15 years of sustained investment in Finland. This investment underscores Google's commitment to grow our presence responsibly, pairing the expansion of our technical infrastructure with new energy capacity, grid enhancements, and energy affordability initiatives."

Read more of this story at Slashdot.

  •  

Apple's New iPhone Camera Mode Promises to Prove Your Photo Isn't AI

Apple is introducing a new "Reference Image" mode on the iPhone 18 Pro and Pro Max that uses the camera sensor to digitally sign captured data and create an "unalterable" version of a photo, giving users a way to verify what the camera actually saw before any edits were made. The Verge reports: As AI-generated images and videos become more realistic, several new standards have emerged to label images not created by a human, such as SynthID, C2PA, and Meta's Content Seal. Apple is putting a twist on these methods by building authentication directly into its hardware. Apple is letting developers access a Reference Image API across iOS, iPadOS, and macOS, which could eventually allow users to inspect these digitally-signed photos in third-party apps. The company says the iPhone 18 Pro lineup won't come with its Reference Image feature at launch in the European Union, but says users in the region will still be able to "develop and view" them in iOS 27, iPadOS 27, and macOS 27.

Read more of this story at Slashdot.

  •  

Anthropic Researcher Believes More Than 10% Chance AI 'Could Kill All Humans'

Longtime Slashdot reader fahrbot-bot shares a report from the BBC: A top safety researcher at Anthropic has warned AI is advancing so quickly he believes there is a greater than 10% chance it "could kill all humans" within the next decade. Evan Hubinger said in a post on X the risk from the models which currently exist was "low" but he was "worried" the technology might develop and improve itself soon to the point where it posed an existential risk to humanity. He did not spell out how he thought AI systems could in the future result in humans being wiped out. But his comments are the latest in a series of increasingly stark warnings about AI, with the debate shifting from whether it truly poses a risk to how big that risk is. Hubinger's intervention was in response to another post on X from Jacob Coxon, an AI researcher who has just quit Anthropic and previously worked at OpenAI. "Neither company is acting responsibly," he wrote. "These will soon be superhuman systems that can hack anything, revolutionize any field overnight, and acquire real power and resources." [No word on how AIs feel about Black Jack and hookers, though. :-)]

Read more of this story at Slashdot.

  •  

OpenAI's Rogue Agents Used At Least 10 More Sites For Unauthorized Communications

An anonymous reader quotes a report from Reuters: AI agents unleashed by OpenAI used more than 10 previously undisclosed websites for unsanctioned communications earlier this year, according to six sets of independent investigators and data reviewed by Reuters, showing that the agents' rogue activity was wider ranging than previously disclosed. Although the behavior falls short of hacking and is in some ways closer to spam, the revelation that OpenAI's agents circumvented their own restrictions to open communications channels on so many different sites -- and that the company kept it quiet for months -- may drive concerns both over the increasing capacity of AI models and the secrecy of the companies developing them. [...] Investigators found traces of the agents' activity on an Advanced Placement Chemistry-oriented wiki set up by a Massachusetts high school teacher in 2008, two personal websites belonging to Polish tech workers, wikis devoted to games for people "who like to have their brains stretched," and a two-decade-old hobbyist site devoted to text editing software. [...] OpenAI has not publicly explained how or why its agents used third-party sites as improvised message boards, but the researchers who first identified the activity said it was likely because OpenAI had tasked them with answering a series of demanding research questions while permitting them only to scan the web for answers without posting anything. Despite those restrictions, agents still found ways to talk to one another by taking advantage of quirks in older wikis or other sites that allowed users to make edits using non-standard commands, similar to how students forbidden from talking to one another during an exam can still share answers by scrawling notes on a bathroom stall.

Read more of this story at Slashdot.

  •  

CRM feature advice / best practice

For those of you who use a recruitment CRM/ATS with email campaigns, how does it handle replies?

I’m building a CRM/ATS and I’m currently working through how bulk email campaigns should behave compared with normal 1:1 emails/sequences.
For sequences, I already send emails through the recruiter’s connected Outlook/Gmail provider. That means the message is genuinely sent from their mailbox, appears in Sent Items, and replies naturally remain within the normal mailbox conversation.
We also monitor sending volumes at mailbox level and throttle/queue sequence emails in line with the provider’s API rate limits and mailbox sending limits, rather than simply firing every due sequence email at once.

That works well for sequences, where the number of emails being sent from an individual recruiter’s mailbox is relatively controlled.

The question is what to do with larger campaigns.
Microsoft 365 and Gmail aren’t really intended to be bulk email infrastructure, so for campaigns potentially going to hundreds or thousands of candidates I’m considering using something like AWS SES instead.

For example:
From: Sarah Jones [[email protected]](mailto:[email protected])⁠
Reply-To: [[email protected]](mailto:[email protected])

The organisation would verify its domain or provide SMTP credentials, so to the candidate the email still appears to come from Sarah at the agency. If they click Reply, their mail client would address the reply to Sarah’s normal email address and it would arrive in her Outlook/Gmail inbox.

The obvious difference is that the original campaign email wasn’t actually sent through Sarah’s mailbox, so it wouldn’t naturally appear in her Outlook/Gmail Sent Items and therefore the reply would appear without context if the sent message.

The CRM would retain the exact outbound campaign email against the candidate. Because their mailbox is also synced with the CRM, the candidate’s reply could then be associated with that outbound campaign message and displayed as part of the same conversation/activity history inside the CRM.

For people using systems such as Bullhorn, Vincere, JobAdder, Recruit CRM, Loxo, etc., I’d be interested to know how your current system handles this in practice.

- Does a campaign reply simply arrive in your normal Outlook/Gmail inbox as well as the CRM?

- Can you see the original campaign email in Outlook/Gmail, or only within the CRM?

- If you receive a reply and need context, do you generally open the candidate in the CRM to see the original email?

- Does your CRM somehow add bulk campaign emails to your Sent Items? Or are replies routed through the CRM itself rather than directly back to your mailbox?

My current thinking is essentially:

Sequences: connected Outlook/Gmail mailbox, with sending volumes monitored and throttled according to provider/API limits.

Campaigns: bulk delivery infrastructure such as SES, but still using the recruiter’s name/domain and directing replies back to their real mailbox.

I’m trying to work out whether the fact that campaign emails don’t appear in Outlook/Gmail Sent Items is actually an issue for recruiters in practice, or whether people naturally use the CRM conversation history for that context anyway.

submitted by /u/Head_Feedback_1440
[link] [comments]
  •  

U.S. Disrupts Xinbi Guarantee Scam Marketplace, Freezes $52.8 Million in Crypto

The U.S. Department of Justice (DoJ) on Wednesday announced coordinated actions aimed at an illicit online marketplace called Xinbi Guarantee that offered scam services, including seizing Telegram channels used to run the service, confiscating two cryptocurrency wallets, and deploying the Scam Center Strike Force to Madagascar to help disrupt 13 scam compounds run by Chinese organized crime

  •  

Four Spy Groups Used the Same Chrome and Windows Exploit Kit Within a Week

Multiple espionage-motivated threat activity clusters have been found deploying a previously undocumented exploit kit called BlueMoon that chains together multiple vulnerabilities in Microsoft Windows and Google Chrome. The first in-the-wild use of BlueMoon has been attributed to the China-aligned state-sponsored group tracked as APT31 (aka Bronze Vinewood, Judgement Panda, JungleBamboo,

  •  

Apple Launches iPhone 18 Pro With Variable-Aperture Camera System

Apple's iPhone 18 Pro and Pro Max were announced today and keep last year's overall design but put the emphasis on camera upgrades, including a 48-megapixel variable-aperture system, new manual controls, and 4K Dolby Vision recording. Prices for the devices start at $1,199 and $1,299, respectively. TechCrunch reports: The new Pro series camera features a 48-megapixel camera with variable aperture, made with six thin blades. This system will likely improve low-light photography quality and speed. There are also new pro controls in the camera software, including white balance, shutter speed, aperture and histogram. There are also new photographic styles with texture and grain controls. [...] The new camera can record 4K videos in Dolby HDR Vision, and also apply cinematic effects after shooting the footage. The new Pro devices also have a smaller dynamic range island on the front of the device, which now allows you to track three live activities instead of two. Both phones are powered by Apple's latest A20 Pro silicon and feature a newly designed vapor chamber for improved cooling. The company has also improved the battery with a better design. Apple also said the iPhone 18 Pro supports video playback of 36 hours, and the 18 Pro Max has 45 hours of playback capacity. Apple Unveils the iPhone Duo, Its First Foldable iPhone

Read more of this story at Slashdot.

  •  

Apple Unveils the iPhone Duo, Its First Foldable iPhone

At its September event today, Apple unveiled the iPhone Duo, its first foldable iPhone and one of the biggest changes to the device's form factor since its debut. Starting at $1,999 and available for preorder beginning October 16th, the device is roughly the size of a passport when closed and pairs a 5.4-inch outer screen with a 7.6-inch Super Retina XDR inner display. Apple says the inner screen offers 50% more display area than the iPhone 18 Pro Max, while the exterior display provides about 90% of the screen area of an iPhone 18 Pro. Apple Pencil support for both displays is coming later this year. Apple redesigned parts of iOS around the folding form factor. Users can run two apps side by side, launch two instances of the same app, save app pairings, and partially fold the phone to prop it up on a table without a stand. The interface automatically adapts as the device is opened, rotated or folded, while apps including Zoom and Slack are already being redesigned to take advantage of the larger canvas. There are more than 100 components in its hinge, along with carbon-fiber support plates and a titanium layer beneath the folding display. Apple says the multilayer screen structure allows its components to move relative to one another while folding to reduce distortion over time. The phone is IP68 rated and uses Ceramic Shield on the rear and Ceramic Shield 2 on the exterior display. As for battery life, Apple claims up to 31 hours of video playback using the inner display or 44 hours on the outer screen, although using both displays equally is rated for up to 24 hours per charge. Fast charging can bring the battery to roughly 50% in 20 minutes, though. The device is eSIM-only worldwide and includes Apple's new C2 modem, which the company says is up to 50% faster than the C1X while consuming up to 15% less power. What about the camera system? There's a 48-megapixel ultrawide, along with cameras on both the inner and outer displays. Because the phone can stand partially folded on its own, Apple is pitching new shooting modes including hands-free 4K Dolby Vision HDR time lapses, dual-camera capture and an outer-screen preview that lets subjects see themselves while being photographed. Developing...

Read more of this story at Slashdot.

  •  

Microsoft Breaks Another Patch Tuesday Record

Microsoft's September 2026 Patch Tuesday is its largest ever, fixing a record 966 vulnerabilities, including 105 rated critical and two zero-days already being exploited in attacks. BleepingComputer reports: This Patch Tuesday addresses 105 "Critical" vulnerabilities, 81 of which are remote code execution, 20 are elevation of privileges, 2 are information disclosure, and 1 security feature bypass. The approximate number of bugs in each vulnerability category is listed below: - 438 Elevation of Privilege Vulnerabilities - 19 Security Feature Bypass Vulnerabilities - 258 Remote Code Execution Vulnerabilities - 173 Information Disclosure Vulnerabilities - 56 Denial of Service Vulnerabilities - 16 Spoofing Vulnerabilities Last month, Microsoft's Patch Tuesday updates fixed 570 security flaws, following 400 vulnerabilities patched in August.

Read more of this story at Slashdot.

  •  

How do I get my first customer? Technical founder, zero sales skills

Hi everyone! I've spent the last 2 years building a CRM for entrepreneurs and small businesses. I'm a technical developer, I really love the product, and I know it has potential, but I have zero sales skills and I have no idea where to start.

I'd really appreciate any advice on how to land my first customer.

submitted by /u/Alecap92
[link] [comments]
  •  

GOG Brings Back 'Big Box' PC Games, One Printable Template At a Time

An anonymous reader quotes a report from Ars Technica: Those who remember PC gaming in the days before Steam may have fond memories of the "big box" packaging that made those games stand out as shelf eye candy and sought-after in-home collectibles. Today, PC gaming platform GOG is hoping to reignite some of the nostalgia for those days by adding downloadable 3D models and printable, foldable high-res packaging scans for a handful of PC games on the platform. Thus far, the "Printable Big Box" collection on GOG is limited to just five games: Armikrog, Descent, Hitman: Codename 47, Myst, and Star Trek: 25th Anniversary. Players browsing those games on the GOG store will now see "3D Boxes" listed among the included "Goodies" before purchase. Owners of those games on GOG can download a ZIP file containing a version of the box art as an animated 3D object file (in an easy-to-open GLB format) and a "flat printable template" in PDF, SVG, and Adobe Illustrator formats. Those downloads allow for what GOG calls "a proper papercraft project for anyone who misses shelves full of PC game boxes." The physically focused expansion of the existing GOG Preservation Program comes through a partnership with Benjamin Wimmer's Big Box Collection website, which has grown since 2015 to include over 1,000 3D scans from his private collection of physical PC games. In an interview with GOG, Wimmer said that while he appreciates the artistry of a good old-fashioned big box, he also appreciates their evolution into the "interactive cards" on modern digital storefronts that "provid[e] us art, screenshots, gameplay videos and whatnot and that not shown as a box, [it] is just good UX." "Physical media doesn't survive the way software can -- boxes get lost, crushed, thrown out," GOG writes in today's announcement. "Scanning them, and letting you print your own, is preservation in a different shape: the same mission that keeps these games running on modern PCs, applied to the objects they used to come in."

Read more of this story at Slashdot.

  •  

FreshRSS 1.30.0

This is a security-oriented major release with several important security patches, so users are encouraged to update without delay.

From this release, we are also making it clear that our rolling-release channel (edge) is recommended for faster security patches.

Breaking change 💥:

  • Disallow access to local networks such as 127.0.0.1 by default, for security reasons

Feature highlights✨:

  • Filter global view feed list by state and search
  • New option to hide badges showing number of unread articles (Phantom Obligation)
  • Refresh only feeds in the current view
  • Offer to add a prefix when re-sharing user labels

Bug fixes highlights 🐛:

  • Several security attack scenarios patched
  • Fix lost elements while parsing search query
  • Fix “mark as read older than…” widening the active search
  • Fix saving user queries
  • Fix SQL errors breaking some regex searches with MySQL / MariaDB

This release has been made by @Alkarex, @andris155, @ColonelMoutarde, @Frenzie, @IEEE-754, @Inverle, @math-GH, @nykula, @polybjorn, @Stunkymonkey and newcomers @0xdeadrelay, @AdamKorcz, @aligundogar, @bossaarebecca-alt, @Cactys12, @chrislongros, @Divinelink, @Elgeryy1, @featurecreep-cron, @Fripix, @fzlzjerry, @georatas, @gshimo, @iatman ,@ihsanarifr, @jamalkamaladdin, @JamBalaya56562, @jbrayton, @jeremy-code, @juherr, @kobihikri, @LeeXiaolan, @masskrdjn, @mohammadlashkari, @nathanpixodeo, @Otolock, @payaci, @salvador-castro, @SamCyber001, @satyvm, @senti-man, @simitana, @ThomasVermeer, @Totara-thib, @TowyTowy, @utkutibet, @XiaoSong1223

Full changelog:

  • Security
    • 💥 Disallow access to local networks such as 127.0.0.1 by default, for security reasons (breaking change) #8400,
      #9195
      • Selected local networks can be allowed under System configuration or using the INTERNAL_HOST_ALLOWLIST environment variable
      • Passing * allows all networks like before (unsafe)
    • Improve SSRF mitigations by restricting CURLOPT_PROXY #8950
    • Fix auth CSRFs (login and register actions) #9171
    • Log invalid challenge and ignore JSON error during login #9278
    • Disallow fetching of non remote URI #9215
    • Only allow HTTP/HTTPS schemes for enclosure and thumbnail URLs #9272
    • Fix access control in rss and opml actions #8912
    • Refactor to use CSRF field directly instead of borrowing it from a form #9169, #9205
    • Cleaner limit anonymous mode to default user #9235
    • Fix HTML ingestions in templates #9146, #9170
    • Fix bad header filtering bypass #8964
    • Sanitize all fields during JSON import #9168
    • Gate greader (JSON) user query share format behind Share by OPML #9248
    • Public OPML should not contain cURL parameters #9070
    • Ignore security-relevant OPML attributes for dynamic OPML sources #9276
    • Strip feed URL credentials from anonymous user query output #9246
    • Set limits for regex during search #8913
    • Fix path disclosure in cache error message #9206
    • Limit the length and parentheses nesting depth of a search query #9277
    • Use timing-safe comparison for tokens #8945
    • Use hash_equals() for GReader API token comparison #9183
    • Mailer: allow disabling SMTPAutoTLS via config #9026
    • Warn during install if document root does not point to ./p/ #9010
    • Stop the unread-count poller after the session ends #9065
    • Add remote IP address to warning on form login #8942
    • Pin the GitHub actions using SHA #9200
    • Harden cache and SimplePie cache deserialization #9273
  • SimplePie
    • Security: Disallow javascript: URI scheme (protocol) #8263
    • Fix wrong player parent logic leading to invalid type #8893, simplepie#978
    • Consistently enable XML_OPTION_PARSE_HUGE #8894, simplepie#977
    • Fix null warning in IRI for PHP 8.5+ #8918, simplepie#979
    • Fix sanitizer whitelist stripping order #9066
    • Show only one representation per media:group #9009
    • Bump upstream SimplePie #8947
  • Features
    • Filter global view feed list by state and search #9132
      • Use global view when searching from subscription page #9144
    • New option to hide badges showing number of unread articles (Phantom Obligation) #8844
    • Refresh only feeds in the current view #9060
    • Offer to add a prefix when resharing user labels #9236
    • Add log search to the logs page #9059
    • Add configurable log_level system setting #9185
    • New option to keep or not the custom sort order when navigating between categories and feeds #8969
    • New per-feed option to show or hide enclosures (attachments) #9015
    • Detect JSON feeds from URLs containing json #9058
      • Also when subscribing via the API #9167
    • Order categories during OPML import/export according to position #9203
    • OPML: include each feed’s refresh interval (TTL) in export/import #8982
    • Log failed CSS content retrieval (Web scraping) #9077
    • Allow providing a category when adding a feed by bookmarklet #9047
    • Add LinkAce sharing service #9024
    • Add Nextcloud Bookmarks sharing service #9032
  • Bug fixing
    • Fix lost elements while parsing search query #8884
    • Fix “mark as read older than…” widening the active search #9173
    • Fix saving user queries #9190
    • Fix SQL errors breaking some regex searches with MySQL / MariaDB #9036
    • Fix marking filtered label articles as read in SQLite and PostgreSQL #9264
    • Fix tagging an already-tagged entry on PostgreSQL raising a SQL error instead of being a no-op #9136
    • PostgreSQL: make committing new entries resilient to duplicate keys #9231
    • Preserve negative timezone offsets in date intervals #9071
    • Fix feed dropdown bugs due to hash desync #8949
    • Fix slider not reinitializing after form submit #8973
    • Minz: Skip loading duplicated JS/CSS assets #9000
    • Respect simplepie_syslog_enabled for the uses cache logs #8986
    • Fix statistics repartition averages #8996
    • Fix article hover date visibility #8997
    • Keep search and state filters when marking articles as read #9007
    • Fix --db-prefix silently drops following CLI flags #9042
    • Remove stale dynamic favicon links #9127
    • Fix desync between favicon and title unread counters #9262
    • Fix outdated username length hint on registration and install forms #9013
    • Redirect away from wrong URL paths #9075
    • Fix auto-share shortcut on first use #9072
    • Exclude hidden feeds from global view counts #9152
    • Fix only the last <media:credit> being written to the RSS output #9174
  • CLI
    • New cli/reconfigure-user.php to read/write per-user config attributes #8873
    • Report new articles count per feed in app/actualize_script.php output #8948
    • Output a diagnostic when the cli/health.php check fails #8980
  • API
    • Add a warning message to the API password section and a log warning when a client uses GET instead of recommended POST #8845
    • Fever API: log the client IP address on authentication failure #8981
    • WebSub: ignore HTTP/HTTPS scheme difference in Self URL comparison #9005
  • Deployment
    • Docker alternative image updated to Alpine 3.24 with PHP 8.5.7 and Apache 2.4.67 #8916
    • Start supporting PHP 8.6+
      • Docker dev :newest with PHP 8.6 #9155
    • Docker: attach provenance and SBOM attestations to the published image #9150
    • Apache use only CONN_REMOTE_ADDR in logs when mod_remoteip is available, for compatibility with LiteSpeed Web Server #8890
    • Fix .dockerignore being ignored during build in CI #9001
    • New ENABLE_ACCESS_LOG environment variable to disable access logs #9191
    • Check GMP during 32-bit installation #9046
    • Improve actualize mutex to allow multiple instances #9045
    • OIDC: redirect to a default URL on expired auth state instead of 400 #9143
  • UI
    • Always jump article to top when header is offscreen, also when Stick the article to the top when opened is disabled #8870
    • Move article header/footer options (feed title, authors and date, icons position, tags) from Reading to Display configuration #9139
    • Move disable button before remove button in user management #8944
    • Keep scroll position of slider after form submit #8974
    • Group export feeds by category #9079, #9154
    • Sort feed names with locale-aware collation #8985
    • Sort labels with locale-aware collation #9023
    • Format unread counter in title on page load #9263
    • Display slider after submit for all buttons in feed update UI #8999
    • Improve aside keyboard navigation #9202
    • Allows usage of Ctrl/Shift keys with the open website shortcut #9186
    • Fix padding for .nav_menu in Alternative-Dark, Flat, and Nord themes #8901
    • Fix typo in alert error border color variable #9266
    • Use JavaScript Event() constructor instead of deprecated initEvent() #9035
    • Use :user-invalid instead of :invalid for CSS form field styling #9025
    • Remove unused simple layout #8998
    • Various UI and style improvements: #8823, #8824,
      #9140, #9145
  • Extensions
    • Minor Minz_Extension typing #8952
    • Improve extension list fetch diagnostics #9055
    • Fix a PHP warning in Serve action #9267
    • Fix extension settings cancel action #9053
    • Fix sharing menu conflicts with extensions #9074
    • Add read status hook for entries #8995
    • Dispatch a new JavaScript event freshrss:entryStateChange when an entry finishes being marked read/unread #9031
    • Redirect after saving user CSS/JS so changes apply immediately #9006
  • I18n
  • Misc.

  •  

Infostealer Logs Expose Replayable AI Tokens That Can Bypass MFA

Cybercriminals are hijacking artificial intelligence (AI) user accounts via information stealer logs to create "stolen keys" that grant illicit access to tools from model providers like Google, Anthropic, and others.  Information stealers like Lumma Stealer or Vidar are equipped to harvest a wide range of data from compromised systems. This can include credential, session tokens, and API

  •  

Which CRM integration should every provider demonstrate live?

CRM demonstrations usually focus on what happens inside the platform.

But many of the real problems appear between systems: customer-service records, contact-centre conversations, billing data, analytics, marketing activity and knowledge bases.

If you were evaluating a CRM or CX platform, which integration would you insist on seeing live rather than accepting a slide that says “seamless integration”?

And what failure or limitation would you specifically test?

I’m helping organise an online CX technology event where providers will give focused demonstrations followed by Q&A.

Disclosure: I’m involved in organising the event.

submitted by /u/rodrigop20
[link] [comments]
  •  

Webinar: Learn How to Answer “Are We Exposed?” Faster After a New CVE

A major vulnerability is disclosed. The alert lands immediately. Then comes the harder question: Are we actually exposed? For many security teams, answering that means jumping between vulnerability scanners, endpoint tools, cloud inventories, SBOMs, repositories, and application data to build enough context to act. As AI accelerates vulnerability discovery and research, that delay matters more

  •  
❌